-
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
JIT: fix jit stress failures in fgSetBlockOrder
#80975
Conversation
Defer asserting that bbNums are ordered until we know if we're optimizing (and hence have computed dominators). Fixes dotnet#80974.
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak Issue DetailsDefer asserting that bbNums are ordered until we know if we're optimizing (and hence have computed dominators). Fixes #80974.
|
PTAL @dotnet/jit-contrib This should fix some of the jitstress issues I caused. |
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress |
Azure Pipelines successfully started running 2 pipeline(s). |
worth adding that into assert? |
We check that just above. |
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.