Rust

6049 readers

97 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago

MODERATORS

[email protected]

Making Rust binaries smaller by default (kobzol.github.io)

submitted 10 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

Upto 90% for hellworld

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 10 months ago (1 children)

So debug builds now strip it by default as well?

[–] [email protected] 9 points 10 months ago (3 children)

It's also what I understood from what I read but I assume it was just a poor choice of word. Debug symbols are way too important for debugging to be stripped by default.

[–] [email protected] 5 points 10 months ago (1 children)

In fact, this new default will be used for any profile which does not enable debuginfo anywhere in its dependency chain, not just for the release profile.

On reflection I imagine the debug profile does enable this

[–] [email protected] 4 points 10 months ago

Yeah, this make sence

[–] [email protected] 4 points 10 months ago* (last edited 10 months ago) (1 children)

As mentioned in the article, this concerns release mode, which already does not have symbols by default for user code. It does have symbols for the standard library code, however, due to how the binaries for the standard library are shipped (i.e. with symbols only). This change simply also removes standard library symbols.

If you need symbols, you can use default debugging build, or if you need both compiler optimizations and debugging symbols you can create a custom profile that inherets from release with debug = true. The second you already need to do to get full debugging symbols right now, so this isn't really much of a change from a workflow standpoint.

[–] [email protected] 2 points 10 months ago* (last edited 10 months ago) (1 children)

In fact, this new default will be used for any profile which does not enable debuginfo anywhere in its dependency chain, not just for the release profile.

This is the sentence that tripped me up. But on rereading I'm assuming the debug profile does enable this.

[–] [email protected] 3 points 10 months ago (1 children)

Yeah, definitely :)

The default dev profile is defined as:

[profile.dev]
opt-level = 0
debug = true
split-debuginfo = '...'  # Platform-specific.
strip = "none"
debug-assertions = true
overflow-checks = true
lto = false
panic = 'unwind'
incremental = true
codegen-units = 256
rpath = false

You can find more information in the cargo book page on profiles

[–] [email protected] 1 points 10 months ago

I knew I had to be missing something. Thanks for the insight mate.

[–] [email protected] 2 points 10 months ago

I guess it may use external debug symbols and strip them from the binary by default.

Otherwise seems like a massive change haha