-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
jitstress-random: Assertion failed 'node->OperIsLIR()' #83332
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak Issue DetailsFailed in two recent runs: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fdbd8b3f6d0c4c0080/JIT.Directed/1/console.64d0864a.log?helixlogtype=result
first appeared in #82731 cc @anthonycanino @tannergooding
|
This looks unrelated to #82731. The EVEX logic is off without a special opt-in and the test in question has no SIMD logic. It looks like this might instead be related to the new In particular, we have
We then have:
In
And at the end of
So between |
@tannergooding What node is it asserting on? Maybe the |
It's asserting on 000124 because its finding the comma as part of validating LIR immediately after rationalization Rationalization itself appears to not hit the comma due to the splitting that happens. |
Ah, then the problem is that we are improperly rethreading the nodes after the splitting, rationalization should not be seeing that node. |
Failed in two recent runs: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fdbd8b3f6d0c4c0080/JIT.Directed/1/console.64d0864a.log?helixlogtype=result
first appeared in #82731 cc @anthonycanino @tannergooding
The text was updated successfully, but these errors were encountered: