optimize release build for size #111
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There's an unstable feature for it: https://doc.rust-lang.org/cargo/reference/unstable.html#profile-strip-option It just merged into rustc so should make it to 1.58 rust-lang/rust#72110 (comment) pr to stabilize in cargo: rust-lang/cargo#10088 |
notgne2
force-pushed
the
optimize-size
branch
from
2e825e3 to
f2a3044
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are few more things we could do to get it a bit lower. We could consider removing the ability to trace in a release build, and just abort, thus removing the need for the stack unwinding code. Also, stripping the binary helped remove about half a MB, but I don't think cargo has a way to do this automatically (that I could find).