-
Notifications
You must be signed in to change notification settings - Fork 5k
Arm: Include BBJ_ALWAYS blocks in dominance calculation #59376
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
Conversation
/azp run runtime-coreclr jitstress |
Azure Pipelines successfully started running 1 pipeline(s). |
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsFor long time in ARM, we have a workaround to add Fixes: #59298
|
/azp list |
/azp run Antigen |
Azure Pipelines successfully started running 1 pipeline(s). |
566aa6b
to
49dcb70
Compare
/azp run runtime-coreclr jitstress |
Azure Pipelines successfully started running 1 pipeline(s). |
@dotnet/jit-contrib , @BruceForstall |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wish we could make this simpler/easier/cleaner, but for now, this LGTM.
/azp run Antigen |
Azure Pipelines successfully started running 1 pipeline(s). |
For long time in ARM, we have a workaround to add
BBJ_ALWAYS
infgEnterBlks
so we do not remove that block and convert the finally intoBBF_RETLESS_CALL
. For that reason, we would not iterate over such blocks while computing the dominance reachability . I double checked and we have enough checks to prevent that from happening. So there is no use of special handling of this scenario during dominance calculation.Fixes: #59298