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

post-opt analysis: fix conditional successor visitation logic #53518

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

aviatesk
Copy link
Member

Previously conditional_successors_may_throw performed post-domination analysis not on the initially specified bb (which was given as the argument), but on those BBs being analyzed that were popped from the work-queue at the time. As a result, there were cases where not all conditional successors were visited.

fixes #53508

Previously `conditional_successors_may_throw` performed post-domination
analysis not on the initially specified `bb` (which was given as the
argument), but on those BBs being analyzed that were popped from the
work-queue at the time. As a result, there were cases where not all
conditional successors were visited.

fixes #53508
@aviatesk aviatesk requested a review from Keno February 29, 2024 00:35
@aviatesk aviatesk merged commit 2501e37 into master Mar 1, 2024
7 checks passed
@aviatesk aviatesk deleted the avi/53508 branch March 1, 2024 00:43
aviatesk added a commit that referenced this pull request Mar 1, 2024
Previously `conditional_successors_may_throw` performed post-domination
analysis not on the initially specified `bb` (which was given as the
argument), but on those BBs being analyzed that were popped from the
work-queue at the time. As a result, there were cases where not all
conditional successors were visited.

fixes #53508
tecosaur pushed a commit to tecosaur/julia that referenced this pull request Mar 4, 2024
…ang#53518)

Previously `conditional_successors_may_throw` performed post-domination
analysis not on the initially specified `bb` (which was given as the
argument), but on those BBs being analyzed that were popped from the
work-queue at the time. As a result, there were cases where not all
conditional successors were visited.

fixes JuliaLang#53508
mkitti pushed a commit to mkitti/julia that referenced this pull request Apr 13, 2024
…ang#53518)

Previously `conditional_successors_may_throw` performed post-domination
analysis not on the initially specified `bb` (which was given as the
argument), but on those BBs being analyzed that were popped from the
work-queue at the time. As a result, there were cases where not all
conditional successors were visited.

fixes JuliaLang#53508
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.

post-opt analysis bug: wrongly refine :consistent of Base._getindex(::Base.OneTo{Int}, ::Int)
2 participants