Uh oh!
There was an error while loading. Please reload this page.
Delete more verification code - #72747
Conversation
ghost
commented
Jul 24, 2022
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsMostly just dead code, the only semantic change is around tailcall checks used for stress, they don't check type compatibility in the strict type system sense anymore. Contributes to #32648.
|
bbf0466 to
f2a4221Comparef2a4221 to
bcea870CompareSingleAccretion
commented
Jul 25, 2022
@dotnet/jit-contrib |
We only use it for tail call stress.
bcea870 to
8059243Comparejakobbotsch
commented
Aug 24, 2022
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress |
|
Azure Pipelines successfully started running 2 pipeline(s). |
AndyAyersMS
commented
Sep 14, 2022
Old jistress logs are gone because of the pipeline shift. Let's bounce this and retrun. |
AndyAyersMS
commented
Sep 14, 2022
AndyAyersMS
commented
Sep 14, 2022
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress |
|
Azure Pipelines successfully started running 2 pipeline(s). |
jakobbotsch
left a comment
There was a problem hiding this comment.
LGTM. The failures look frozen object related which should have been fixed already. Thanks for this cleanup.
Mostly just dead code, the only semantic change is around tailcall checks used for stress, they don't check type compatibility in the strict type system sense anymore.
Contributes to #32648.
No diffs (modulo a small TP win).