-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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: Always aggressively compact blocks #109521
JIT: Always aggressively compact blocks #109521
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
cc @dotnet/jit-contrib, @AndyAyersMS PTAL. Small diffs from LSRA churn -- Linux x64 diffs seem to be inflated by duplicate entries in
TP diffs seem to be inflated on non-Windows platforms by some outlier methods in |
Re: the TP outlier, the method with the most basic blocks in Since this is an extreme case, I don't think it warrants changing our compaction strategy, though since we seem to compact chains of blocks with some frequency, it might be worth looking into deferring flow edge updates to reduce duplicated work; I'll keep this in mind when we start rewriting |
ping @AndyAyersMS |
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.
Can you add a note to #107749 so we don't forget about fixing the big fan-in case?
Sure thing; added. |
/ba-g blocked by build timeout |
Part of #107749. Now that we only run block layout in the backend, we can freely compact all compactable blocks in the frontend without worrying about churning layout.