unexpand: save stack size - perf +6.98%#11787
Conversation
Merging this PR will not alter performance
Comparing Footnotes
|
This comment was marked as outdated.
This comment was marked as outdated.
628fe47 to
e6c1c8f
Compare
|
GNU testsuite comparison: |
|
i wasn't expecting such wins for this kind of changes |
|
I don't understand why changing stack allocation to heap allocation is a performance improvement. Additionally, it may be possible that this isn't an improvement on targets other than |
|
I'm OK to have cfg block. |
|
It would be good to understand why there is a performance difference; if necessary this could be reported upstream. |
|
done at rust-lang/rust#148670 |
Please add a comment linking to this issue; it would also have been helpful to include it in the PR description. |
|
I guess it would be good to explain in the comment that the regression is specifically with codegen-units=1 + LTO. |
|
GNU testsuite comparison: |
Like efd0f0c, or just |
|
I think cfg is overkill considering Linux-x64 is most common target (until targets significally decreasing perf was found). |
|
This change is a workaround for an upstream issue and should not be applied to targets where the issue has not been demonstrated. |
This comment was marked as resolved.
This comment was marked as resolved.
|
I guess this is no longer needed as #11806 fixed stack spill. But I'll check CodSpeed few times before closing. |
|
@oech3 Thanks for looking into this! |
Replace a stack array with vec to avoid stack spill seen at rust-lang/rust#148670 .
Probally fixes #10654