-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Inliner uses capacity of locals table instead of count #69280
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsI noticed in #69117 (comment) that we are using runtime/src/coreclr/jit/inlinepolicy.cpp Lines 1708 to 1714 in 96db556
That seems strange and might cause significantly different inlining decisions just by adding or removing very few locals, depending on whether we grow the table one more time or not.
|
@EgorBo please take a look once you're back. |
Decided to postpone this to 8.0 where I plan more changes for the inliner. I tried this locally and it was too impactful |
I noticed in #69117 (comment) that we are using
lvaTableCnt
instead oflvaCount
here:runtime/src/coreclr/jit/inlinepolicy.cpp
Lines 1708 to 1714 in 96db556
That seems strange and might cause significantly different inlining decisions just by adding or removing very few locals, depending on whether we grow the table one more time or not.
category:correctness
theme:inlining
skill-level:intermediate
cost:medium
impact:medium
The text was updated successfully, but these errors were encountered: