Skip to content

Make BroadcastIndexesRange efficient if there is no broadcasting #9298

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Mar 18, 2025

Conversation

swolchok
Copy link
Contributor

It seems to be OK to just check for broadcasting when creating the
iterator and then leave a highly-predictable branch inside the
loop. Avoids code near-duplication to handle both broadcast and
non-broadcast cases.

[ghstack-poisoned]
Copy link

pytorch-bot bot commented Mar 14, 2025

🔗 Helpful Links

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

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

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 Mar 14, 2025
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
[ghstack-poisoned]
@swolchok
Copy link
Contributor Author

noting CI is green before rebasing due to spurious conflicts before land

[ghstack-poisoned]
[ghstack-poisoned]
Base automatically changed from gh/swolchok/375/head to main March 18, 2025 16:24
@swolchok swolchok requested a review from larryliu0820 as a code owner March 18, 2025 16:24
@swolchok swolchok merged commit 89a0bdf into main Mar 18, 2025
76 checks passed
@swolchok swolchok deleted the gh/swolchok/369/head branch March 18, 2025 16:24
oscarandersson8218 pushed a commit to oscarandersson8218/executorch that referenced this pull request Mar 21, 2025
…orch#9298)

It seems to be OK to just check for broadcasting when creating the
iterator and then leave a highly-predictable branch inside the
loop. Avoids code near-duplication to handle both broadcast and
non-broadcast cases.
DannyYuyang-quic pushed a commit to CodeLinaro/executorch that referenced this pull request Apr 2, 2025
…orch#9298)

It seems to be OK to just check for broadcasting when creating the
iterator and then leave a highly-predictable branch inside the
loop. Avoids code near-duplication to handle both broadcast and
non-broadcast cases.
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. topic: not user facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants