Skip to content

Commit e459ff0

Browse files
authored
Rollup merge of #137685 - lqd:nostart-stop-gc, r=petrochenkov
self-contained linker: conservatively default to `-znostart-stop-gc` To help stabilization, this PR disables an LLD optimization with respect to `--gc-sections` and encapsulation symbols: it will reduce the number of crates needing to opt-out of lld due to this bfd / lld difference. For example, all the people using [linkme](https://github.com/dtolnay/linkme), which [doesn't work with lld](dtolnay/linkme#63) or on nightly, need to disable lld. More information about all this, and the historical differences, can be found in: - https://maskray.me/blog/2021-01-31-metadata-sections-comdat-and-shf-link-order - https://lld.llvm.org/ELF/start-stop-gc This optimization has [no visible impact](#137685 (comment)) on our benchmarks, so we can use it by default and have a safer/more conservative starting point to remove friction during migration. We can them emit an FCW for the cases where lld detects reliance on encapsulation symbols without `-znostart-stop-gc`, and then revert back to lld's default after a while. No one compiling on nightly relies on this difference, obviously, so doing an FCW is not necessary until after lld is used on stable. I've tested that this correctly links on `linkme` examples. I've also quickly tried to crate an rmake test but the setup with encapsulation symbols is annoying to reproduce: a few link section/name attributes is not enough, we also need to collect symbols between the encapsulation symbols, without referencing them in code, for `-znostart-stop-gc` to only impact this... It should of course be doable though, maybe ``@Kobzol`` will look into it if they have time. r? ``@petrochenkov``
2 parents 0386e93 + 762fdf6 commit e459ff0

File tree

1 file changed

+26
-0
lines changed
  • compiler/rustc_codegen_ssa/src/back

1 file changed

+26
-0
lines changed

compiler/rustc_codegen_ssa/src/back/link.rs

+26
Original file line numberDiff line numberDiff line change
@@ -3438,6 +3438,32 @@ fn add_lld_args(
34383438
// this, `wasm-component-ld`, which is overridden if this option is passed.
34393439
if !sess.target.is_like_wasm {
34403440
cmd.cc_arg("-fuse-ld=lld");
3441+
3442+
// GNU ld and LLD have opposite defaults on some section garbage-collection features. For
3443+
// example, the somewhat popular `linkme` crate and its dependents rely in practice on this
3444+
// difference: when using lld, they need `-z nostart-stop-gc` to prevent encapsulation
3445+
// symbols and sections from being garbage-collected.
3446+
//
3447+
// More information about all this can be found in:
3448+
// - https://maskray.me/blog/2021-01-31-metadata-sections-comdat-and-shf-link-order
3449+
// - https://lld.llvm.org/ELF/start-stop-gc
3450+
//
3451+
// So when using lld, we restore, for now, the traditional behavior to help migration, but
3452+
// will remove it in the future.
3453+
// Since this only disables an optimization, it shouldn't create issues, but is in theory
3454+
// slightly suboptimal. However, it:
3455+
// - doesn't have any visible impact on our benchmarks
3456+
// - reduces the need to disable lld for the crates that depend on this
3457+
//
3458+
// Note that lld can detect some cases where this difference is relied on, and emits a
3459+
// dedicated error to add this link arg. We could make use of this error to emit an FCW. As
3460+
// of writing this, we don't do it, because lld is already enabled by default on nightly
3461+
// without this mitigation: no working project would see the FCW, so we do this to help
3462+
// stabilization.
3463+
//
3464+
// FIXME: emit an FCW if linking fails due its absence, and then remove this link-arg in the
3465+
// future.
3466+
cmd.link_arg("-znostart-stop-gc");
34413467
}
34423468

34433469
if !flavor.is_gnu() {

0 commit comments

Comments
 (0)