-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 failure from recent pred list changes #80974
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak Issue DetailsThis is affecting about 150 test executions in jitstress and some in libraries jitstress too
There is an assert in
|
Likely caused by #80891 |
Defer asserting that bbNums are ordered until we know if we're optimizing (and hence have computed dominators). Fixes dotnet#80974.
Defer asserting that bbNums are ordered until we know if we're optimizing (and hence have computed dominators). Fixes #80974.
Defer asserting that bbNums are ordered until we know if we're optimizing (and hence have computed dominators). Fixes dotnet#80974.
This is affecting about 150 test executions in jitstress and some in libraries jitstress too
There is an assert in
optReachWithoutCall
invoked byfgSetBlockOrder
that is triggered because we no longer have bbNum order in some unoptimized compiles. Turns out we don't actually depend on block order so I think I can just defer the assert.The text was updated successfully, but these errors were encountered: