Skip to content

Qualcomm AI Engine Direct - Cast TopK int64 indices to int32 - #24054

Open
msluszniak wants to merge 1 commit into
pytorch:mainfrom
msluszniak:ms/qnn-topk-int64-indices
Open

msluszniak wants to merge 1 commit into
pytorch:mainfrom
msluszniak:ms/qnn-topk-int64-indices

Conversation

@msluszniak

@msluszniak msluszniak commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

QNN TopK writes int32 indices, but I64toI32 kept their getitem int64 (the upstream TODO "support OP such as topK"), so delegated indices came back half zeros and CPU TopK indices broke a delegated consumer. I64toI32 now casts the int64 outputs of TopK to int32 at the getitem.

Test plan

New TestQNNFloatingPointModel::test_qnn_backend_topk_indices and test_qnn_backend_topk_on_cpu_and_index fail on main and pass here (x86 simulator). test_passes.py, rework/passes/test.py (debug-handle maps updated for the new cast) give the same results as main; TestQNNFloatingPointModel passes.

cc @cccclai @winskuo-quic @shewu-quic @haowhsu-quic @DannyYuyang-quic @cbilgin @abhinaykukkadapu @psiddh @nil-is-all

QNN TopK writes int32 indices, but I64toI32 left the getitem of the indices
declared int64, so a delegate output read them as int64 (half the values wrong) and
a TopK left on CPU fed int64 into a delegated consumer. I64toI32 now casts the
int64 outputs of multi-output ops (TopK) to int32 at their getitem.
@msluszniak
msluszniak requested a review from psiddh as a code owner October 21, 2026 09:53
@pytorch-bot

pytorch-bot Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 4 New Failures

As of commit ec55c2b with merge base e6cfbf8 (image):

NEW FAILURES - The following jobs have failed:

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

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 21, 2026
@github-actions

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@executorch-triage executorch-triage Bot added the community: contribution PRs coming from community (excluding hardware partners) label Oct 21, 2026
@nil-is-all nil-is-all added partner: qualcomm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Qualcomm module: qnn Issues related to Qualcomm's QNN delegate and code under backends/qualcomm/ labels Oct 21, 2026
borys3kk pushed a commit to borys3kk/swm_executorch that referenced this pull request Oct 22, 2026
QNN TopK writes int32 indices, but I64toI32 left the getitem of the indices
declared int64, so a delegate output read them as int64 (half the values wrong) and
a TopK left on CPU fed int64 into a delegated consumer. I64toI32 now casts the
int64 outputs of multi-output ops (TopK) to int32 at their getitem.

Backport of pytorch/executorch#24054. 1.4.1 has no rework pass tests.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. community: contribution PRs coming from community (excluding hardware partners) module: qnn Issues related to Qualcomm's QNN delegate and code under backends/qualcomm/ partner: qualcomm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Qualcomm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants