JIT: fix assert in assertion prop#106146
Merged
AndyAyersMS merged 1 commit intodotnet:mainfrom Aug 8, 2024
Merged
Conversation
'optAssertionPropGlobal_RelOp' had branch where it was expecting both op2 and op1 to be locals, but only had verified that op2 was. Add an extra check. Fixes dotnet#105670
Member
Author
|
@jakobbotsch PTAL No diffs expected. |
tannergooding
approved these changes
Aug 8, 2024
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
optAssertionPropGlobal_RelOphad branch where it was expecting both op2 and op1 to be locals, but only had verified that op2 was.Add an extra check.
Fixes #105670