-
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
Enable JitDasmWithAlignmentBoundaries and JitDasmWithAddress in Release #82666
Enable JitDasmWithAlignmentBoundaries and JitDasmWithAddress in Release #82666
Conversation
@kunalspathak @dotnet/jit-contrib PTAL |
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.
Awesome!
How much would it take to also enable JitDiffableDasm=1
? (not necessarily in this PR)
I'm wondering if we should rename these variables at the same time to have consistent naming conventions across the board -- i.e. |
Done!
Great idea! Any concerns, @dotnet/jit-contrib? I hope it doesn't break your internal tooling. We can maintain old names too in that case. DOTNET_JitDisasm
-DOTNET_JitDiffableDasm
+DOTNET_JitDisasmDiffable
-DOTNET_JitDasmWithAlignmentBoundaries
+DOTNET_JitDisasmWithAlignmentBoundaries The idea that all JitDisasm related configs now easier to find |
jitutils will need a few updates too. |
Looks like FILECHECK is also unhappy |
43edcae
to
e01be9c
Compare
Changes looks fine to me. Just make sure to update jitutils as @jakobbotsch said before merging this. |
It has to be done to update - e.g. currently FILECHECK uses old name to run tests, I can't update it in parallel. So I'm going to merge this as is, then update tools, propagate them all the way down to this repo and then remove old env var names.
Yeah it had an impact but we didn't notice it in any of our TP-related benchmarks (like crossgen, time-to-first request, etc). So I'm going to merge this as is and then land a quick TP improvement I noticed that is sort of related |
I think it should be easy to get rid of the TP regression by moving the checks under the existing release |
61dfbcd
to
5452a2c
Compare
Merging, TP regressions are mitigated by Jakob's suggestion: https://dev.azure.com/dnceng-public/public/_build/results?buildId=193118&view=ms.vss-build-web.run-extensions-tab |
This PR enables
DOTNET_JitDiffableDasm
andDOTNET_JitDasmWithAlignmentBoundaries
for Release. As they're now public, they're also renamed for better name consistency:JitDiffableDasm
is useful to compare codegens.JitDasmWithAlignmentBoundaries
is useful to debug loop alignment and JCC-erratum issuesDefault JitDisasm
DOTNET_JitDisasmDiffable=1
DOTNET_JitDisasmWithAlignmentBoundaries=1