GSA: Fix iterator invalidation when expanding gamma trees#672
Merged
AyaElAkhras merged 6 commits intomainfrom Jan 17, 2026
Merged
GSA: Fix iterator invalidation when expanding gamma trees#672AyaElAkhras merged 6 commits intomainfrom
AyaElAkhras merged 6 commits intomainfrom
Conversation
Member
|
Thanks for reporting this, I see the issue. Just one thing to double-check: all of the gates added by |
Collaborator
Author
Yes, exactly. |
AyaElAkhras
approved these changes
Jan 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While iterating over
gatesPerBlockinsideconvertPhiToGammafunction, the gamma expansion logic may insert newentries into the same DenseMap. This can invalidate iterators and lead to
crashes in specific CFG/GSA patterns. The iteration is now performed over a
stable copy so that gatesPerBlock can be safely extended during gamma
expansion.
P.S. This still needs to be tested on all integration tests; once that is
done, the PR will be marked as non-draft.