JIT: Fix alignment insertion assuming only emitForceNewIG can create new IGs #73518
Conversation
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
ghost
added
the
area-CodeGen-coreclr
jakobbotsch
changed the title
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsIssue I noticed over in #73365.
|
|
I realize there is |
This was referenced Aug 8, 2022
ghost
locked as resolved and limited conversation to collaborators
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.
Issue I noticed over in #73365.
emitNewInstrAligncan create new IGs for other reasons thanemitForceNewIG, e.g. if the current IG cannot fit anotherinstrDescor if we have reached the limit on the number of instructions in the current IG (255).