-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Keep the volatility of CLS_VAR
s in rationalization
#65919
Conversation
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsWe're expecting some negative diffs on ARM. One more step towards
|
@dotnet/jit-contrib |
if (isVolatile) | ||
{ | ||
assignment->gtFlags |= GTF_IND_VOLATILE; | ||
} | ||
|
||
// TODO: JIT dump |
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.
wonder what that is supposed to mean 😄
@@ -453,11 +453,18 @@ void Rationalizer::RewriteAssignment(LIR::Use& use) | |||
|
|||
case GT_CLS_VAR: | |||
{ | |||
bool isVolatile = (location->gtFlags & GTF_CLS_VAR_VOLATILE) != 0; | |||
|
|||
location->gtFlags &= ~GTF_CLS_VAR_VOLATILE; |
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 it required to reset GTF_CLS_VAR_VOLATILE
?
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.
Not strictly, no one will look at it once it becomes CLS_VAR_ADDR
, but it's good practice to clear flags when bashing to an oper that doesn't support them.
Some expected negative diffs on ARM.
One more step towards
CLS_VAR
deletion.