-
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
[release/6.0] JIT: don't clone loops where init or limit is a cast local #57685
Conversation
The loop cloner assumes all computations it introduces are compatible with TYP_INT, so don't allow cloning when the initial or final value are variables with incompatible types. Fixes #57535.
Co-authored-by: SingleAccretion <62474226+SingleAccretion@users.noreply.github.com>
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsBackport of #57602 to release/6.0 /cc @AndyAyersMS Customer ImpactTestingRisk
|
cc @dotnet/jit-contrib @jeffschwMSFT I take it we're supposed to label the issue with "blocking-release" and perhaps not the PR..? |
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.
LGTM
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.
Approved. We can merge once we have a green ci.
Should we consider this for RC1?
This was reported by an internal customer on 6p7 so we should try and get it into RC1. |
Mono -llvm failing on CSCBench arm64"
|
Backport of #57602 to release/6.0
/cc @AndyAyersMS
Customer Impact
Already reported by one customer (in 6p7). Caused crossgen2 to fail.
Testing
Verified it fixes the customer issue, plus new tests added. No diffs in existing tests (per SPMI).
Risk
Low, this is a change to disable an optimization in an uncommon situation.