-
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
Introduce fgDebugCheckTypes #94621
Introduce fgDebugCheckTypes #94621
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsValidate types used in IR nodes. Also, remove PS: plan to remove the GT_HWINTRINSIC quirk as part of this PR.
|
4536077
to
17b1a17
Compare
/azp list |
This comment was marked as resolved.
This comment was marked as resolved.
/azp run runtime-coreclr outerloop, runtime-coreclr jitstress, runtime-coreclr pgo |
Azure Pipelines successfully started running 3 pipeline(s). |
e517b77
to
ecc5d6e
Compare
the latest diffs are better https://dev.azure.com/dnceng-public/public/_build/results?buildId=467438&view=ms.vss-build-web.run-extensions-tab but there are still regressions because of GT_HWINTRINSIC (mainly around op_Equality) |
@jakobbotsch @dotnet/jit-contrib PTAL Small diffs are caused by the Size regressions on arm64 seem to be perf improvements - optOptimizeBool kicks in where previously it didn't, e.g.:
Main:
PR:
|
Thanks for doing this! I'm looking forward to all the follow-up work on the TODOs :-) |
varTypeIsSmallInt
because it's the same asvarTypeIsSmall
.varTypeGCtype
because it's the same asvarTypeGC
ubyte GT_OR(op1, op2) ...
)