Skip to content
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

Bounds visitors for min/max were missing single_point mutated case #7377

Merged
merged 2 commits into from
Feb 25, 2023

Conversation

abadams
Copy link
Member

@abadams abadams commented Feb 24, 2023

Other visitors handle this case, but it was inexplicably missing from min/max. This causes later checks to is_single_point to suboptimally return false because we get two distinct but equal Exprs.

Partially fixes #7374

Copy link
Contributor

@steven-johnson steven-johnson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a test for this?

@abadams
Copy link
Member Author

abadams commented Feb 24, 2023

I'm not sure how I'd repro in a small test - it only showed up as suboptimal-but-still-correct lowering in a complex pipeline. Given that this just makes these visitors match their neighbors, I'm inclined to not add a specific test for this.

@abadams
Copy link
Member Author

abadams commented Feb 24, 2023

Actually I just figured it out, so small test incoming...

@abadams abadams merged commit 09400f6 into main Feb 25, 2023
ardier pushed a commit to ardier/Halide-mutation that referenced this pull request Mar 3, 2024
…alide#7377)

* Bounds visitors for min/max were missing single_point mutated case

Partially fixes halide#7374

* Add test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inefficient loops generated with 2D RDom
2 participants