Update Qnnpack Fully Connected Sparse Op to Store Variable Size Indices

[salilsdesai]

Stack from ghstack (oldest at bottom):

• Use Variable Size Indices in Sparse Qlinear Code #85247
• Enable 16bit and 8bit Row/Col Indices in Qnnpack Fully Connected Sparse Op #85246
• Add 16bit and 8bit row/col indices q8gemm sparse kernels #85245
• Enable Running Variable Size Row/Col Indices q8gemm Sparse Kernels in QNNPACK #85244
• -> Update Qnnpack Fully Connected Sparse Op to Store Variable Size Indices #85243

Only uint32_t is supported for now, but uint16_t and uint8_t support will be added in future diffs.

Differential Revision: D38828545

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/85243

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit c61b975:
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: salilsdesai / name: Salil Desai (a569d68, a2ae72e, 8b91d8f, f1f33d4, ee51110, a38658d)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: salilsdesai / name: Salil Desai (a569d68, a2ae72e, 8b91d8f, f1f33d4, ee51110, a38658d)

[facebook-github-bot]

/easycla

As part of the transition to the PyTorch Foundation, this project now requires contributions be covered under the new CLA. See #85559 for additional details.

This comment will trigger a new check of this PR. If you are already covered, you will simply see a new "EasyCLA" check that passes. If you are not covered, a bot will leave a new comment with a link to sign.

[facebook-github-bot]

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[github-actions]

Hey @salilsdesai.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.