[VectorCombine] Avoid double deletion in eraseInstruction
#155621
Merged
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.
Consider the following pattern:
As
Eis dead, we calleraseInstruction(E)and see if its operands become dead.RecursivelyDeleteTriviallyDeadInstructions(D)also erasesC, which causes a UAF crash in the subsequent callRecursivelyDeleteTriviallyDeadInstructions(C).This patch also adds deleted ops into the visit list to avoid double deletion. As an alternative, we can use
WeakVHfor the operand list.Closes #155543.