-
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
Delete more verification code #72747
Delete more verification code #72747
Conversation
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
f2a4221
Compare
f2a4221
to
bcea870
Compare
@dotnet/jit-contrib |
We only use it for tail call stress.
bcea870
to
8059243
Compare
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress |
Azure Pipelines successfully started running 2 pipeline(s). |
Old jistress logs are gone because of the pipeline shift. Let's bounce this and retrun. |
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress |
Azure Pipelines successfully started running 2 pipeline(s). |
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. 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).