-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Reduce monomorphisation bloat in small_c_string #121101
Conversation
rustbot has assigned @Mark-Simulacrum. Use r? to explicitly pick a reviewer |
This comment has been minimized.
This comment has been minimized.
The Miri subtree was changed cc @rust-lang/miri |
I'm curious if this drops the size of build artifacts. The design sounds like a good tradeoff even if the size decrease is not very significant. |
This comment has been minimized.
This comment has been minimized.
Reduce monomorphisation bloat in small_c_string This is a code path usually next to an FFI call, so taking the `dyn` slowdown for the 1159 llvm-line (fat lto, codegen-units 1, release build) drop in my testing program [t2fanrd](https://github.com/GnomedDev/t2fanrd) is worth it imo.
Yeah, it should. In fact |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Reduce monomorphisation bloat in small_c_string This is a code path usually next to an FFI call, so taking the `dyn` slowdown for the 1159 llvm-line (fat lto, codegen-units 1, release build) drop in my testing program [t2fanrd](https://github.com/GnomedDev/t2fanrd) is worth it imo.
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (5008444): comparison URL. Overall result: no relevant changes - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 636.575s -> 635.882s (-0.11%) |
This comment has been minimized.
This comment has been minimized.
0390ec3
to
f59822c
Compare
@saethlin I tried |
This comment has been minimized.
This comment has been minimized.
Okay, turns out |
What exact size diff with this PR for your examples? |
@klensy With the settings in the PR description, testing the master branch at the time of branch off (eeeb021) vs this PR. |
…trieb Reduce monomorphisation bloat in small_c_string This is a code path usually next to an FFI call, so taking the `dyn` slowdown for the 1159 llvm-line (fat lto, codegen-units 1, release build) drop in my testing program [t2fanrd](https://github.com/GnomedDev/t2fanrd) is worth it imo.
I mean. resulting file size diff, not llvm-lines. |
Without stripping, binary size for t2fanrd goes from |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
217e9c9
to
dbb15fb
Compare
@Nilstrieb rebased and did more find/replace for the last couple invocations, can I get another approval? |
random platforms failing, as expected^^ @bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (6122397): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 641.709s -> 640.336s (-0.21%) |
This is a code path usually next to an FFI call, so taking the
dyn
slowdown for the 1159 llvm-line (fat lto, codegen-units 1, release build) drop in my testing program t2fanrd is worth it imo.