Skip to content

Conversation

@pytorchbot
Copy link
Collaborator

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #11869 by @larryliu0820
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/larryliu0820/67/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/larryliu0820/67/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/gh/larryliu0820/66/orig
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/larryliu0820/67/orig
@diff-train-skip-merge

Pull Request resolved: #11861

Refactoring `op_arange.cpp` to expose `compute_arange_out_size` and `arange_out_impl` for LLM runner to use. See next PR on how to use them.

ghstack-source-id: 292529866
@exported-using-ghexport

Differential Revision: [D77184741](https://our.internmc.facebook.com/intern/diff/D77184741/)
Pull Request resolved: #11869

For huggingface models, `forward()` is taking `tokens` as well as `cache_positions`, which is a list of cache indices. This is different than the .pte files `export_llama` gives, which are taking `tokens` and `input_pos` where `input_pos` is a scalar tensor.

This PR adds support inside `text_decoder_runner.cpp` to handle both shapes of `input_pos`/`cache_positions`.

To make the logic more generic without relying on extra metadata, here I'm adding the logic of inspecting method meta and input tensor info, to make a decision if we want to feed in `input_pos` or `cache_position`.
ghstack-source-id: 292560636
@exported-using-ghexport

Differential Revision: [D77203700](https://our.internmc.facebook.com/intern/diff/D77203700/)
@pytorch-bot
Copy link

pytorch-bot bot commented Jun 25, 2025

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

⏳ No Failures, 5 Pending

As of commit a033c63 with merge base 8b3b028 (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot facebook-github-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 Jun 25, 2025
Base automatically changed from gh/larryliu0820/66/orig to main June 25, 2025 18:13
@larryliu0820 larryliu0820 added the release notes: none Do not include this in the release notes label Jun 27, 2025
@larryliu0820 larryliu0820 merged commit c5ecea6 into main Jun 27, 2025
103 checks passed
@larryliu0820 larryliu0820 deleted the gh/larryliu0820/67/orig branch June 27, 2025 17:21
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. release notes: none Do not include this in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants