-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Linux/arm: LSRA resolution issues #109173
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
…f its association with busy lower-half register (dotnet#107714)" This reverts commit f1bcbeb.
…ng resolution (dotnet#107493)" This reverts commit ac4b7c6.
/azp run Fuzzlyn |
/azp run Antigen |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Fuzzlyn |
/azp run Antigen |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Fuzzlyn |
/azp run Antigen |
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
@AndyAyersMS @dotnet/jit-contrib PTAL |
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.
Is this a candidate for back porting?
Not really, for the same reason as #105619 (comment). |
No antigen/fuzzlyn failures on linux/arm |
Replaces #107904
There are few places where if one-half of the double register is freed up, we need to also check if the other half can be freed up, if that is one of the target register for the resolution. We were already doing at one place, but when we do the resolution using temporary register, we should do the same thing. And lastly, the condition I was using to free the other half in #107714 was not sufficient leading to failures which is also fixed in this PR with the same logic.
Fixes: #107841