-
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
JIT: broaden cloning invariant checks #70232
JIT: broaden cloning invariant checks #70232
Conversation
Streamline call effects checks. Use wider bit vectors. Closes dotnet#70100.
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsStreamline call effects checks. Use wider bit vectors. Closes #70100.
|
Unsurprisingly, leads to more cloning. Some fairly sizeable regressions. We probably need to consider backing off cloning really large loops, especially if evidence of benefit is thin. @BruceForstall PTAL |
// If caller is worried about possible indirect effects, check | ||
// what we know about the calls in the loop. | ||
// | ||
if (inds != 0) |
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.
Are any of the callers worried?
(I do not see us pass anything but VR_NONE
for inds
).
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.
You're right, nobody actually cares right now. And there are other parts of the analysis that are likewise unused.
I'm deliberately leaving it for now. It's possible we'll run across cases where we want to try and use it for something.
Failure is #70305. |
Streamline call effects checks. Use wider bit vectors.
Closes #70100.