-
Notifications
You must be signed in to change notification settings - Fork 250
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
Track binary size impact on Rust executables #541
Comments
So approximately 30KiB. Repo of interest with further information: https://gitlab.com/detly/prod-self-test |
Thanks for reporting this! If it helps, here's a breakdown from
|
Note that this measurement, in order to be effective, requires:
|
It's in the works (Kobzol#1), but I need to resolve rust-lang/rust#101691 first to avoid rebuilding the whole compiler on CI. |
Would it be possible to use -Zbuild-std and patch backtrace into the sources used by that? |
to my knowledge, build-std does not allow patching the standard library sources. rust-lang/wg-cargo-std-aware#7 |
Rust's backtrace implementation is a significant factor in how large every Rust binary is. We should be testing to see how much commits here regress binary size for stdlib-using binaries, before we land them. We may be able to
baitinvite some people working on rustc-perf to help us investigate this issue. It is very likely a size increase due to recent commits created a notable regression, although one that was probably worth the price if so.The text was updated successfully, but these errors were encountered: