rustc will use rust-lld by default on x86_64-unknown-linux-gnu on nightly to significantly reduce linking times.rustc will use rust-lld by default on x86_64-unknown-linux-gnu on nightly to significantly reduce linking times.

rust-lld: How It Can Give You Faster Linking Times

TL;DR: rustc will use rust-lld by default on x86_64-unknown-linux-gnu on nightly to significantly reduce linking times.

Some context

Linking time is often a big part of compilation time. When rustc needs to build a binary or a shared library, it will usually call the default linker installed on the system to do that (this can be changed on the command-line or by the target for which the code is compiled).

\ The linkers do an important job, with concerns about stability, backwards-compatibility and so on. For these and other reasons, on the most popular operating systems they usually are older programs, designed when computers only had a single core. So, they usually tend to be slow on a modern machine. For example, when building ripgrep 13 in debug mode on Linux, roughly half of the time is actually spent in the linker.

\ There are different linkers, however, and the usual advice to improve linking times is to use one of these newer and faster linkers, like LLVM's lld or Rui Ueyama's mold.

\ Some of Rust's wasm and aarch64 targets already use lld by default. When using rustup, rustc ships with a version of lld for this purpose. When CI builds LLVM to use in the compiler, it also builds the linker and packages it. It's referred to as rust-lld to avoid colliding with any lld already installed on the user's machine.

\ Since improvements to linking times are substantial, it would be a good default to use in the most popular targets. This has been discussed for a long time, for example in issues #39915 and #71515, and rustc already offers nightly flags to use rust-lld.

\ By now, we believe we've done all the internal testing that we could, on CI, crater, and our benchmarking infrastructure. We would now like to expand testing and gather real-world feedback and use-cases. Therefore, we will enable rust-lld to be the linker used by default on x86_64-unknown-linux-gnu for nightly builds.

Benefits

While this also enables the compiler to use more linker features in the future, the most immediate benefit is much improved linking times.

\ Here are more details from the ripgrep example mentioned above: linking is reduced 7x, resulting in a 40% reduction in end-to-end compilation times.

Before/after comparison of a ripgrep debug build

Most binaries should see some improvements here, but it's especially significant with e.g. bigger binaries, or when involving debuginfo. These usually see bottlenecks in the linker.

\ Here's a link to the complete results from our benchmarks.

\ If testing goes well, we can then stabilize using this faster linker by default for x86_64-unknown-linux-gnu users, before maybe looking at other targets.

Possible drawbacks

From our prior testing, we don't really expect issues to happen in practice. It is a drop-in replacement for the vast majority of cases, but lld is not bug-for-bug compatible with GNU ld.

\ In any case, using rust-lld can be disabled if any problem occurs: use the -Z linker-features=-lld flag to revert to using the system's default linker.

\ Some crates somehow relying on these differences could need additional link args. For example, we saw <20 crates in the crater run failing to link because of a different default about encapsulation symbols: these could require -Clink-arg=-Wl,-z,nostart-stop-gc to match the legacy GNU ld behavior.

\ Some of the big gains in performance come from parallelism, which could be undesirable in resource-constrained environments.

Summary

rustc will use rust-lld on x86_64-unknown-linux-gnu nightlies, for much improved linking times, starting in tomorrow's rustup nightly (nightly-2024-05-18). Let us know if you encounter problems, by opening an issue on GitHub.

\ If that happens, you can revert to the default linker with the -Z linker-features=-lld flag. Either by adding it to the usual RUSTFLAGS environment variable, or to a project's .cargo/config.toml configuration file, like so:

[target.x86_64-unknown-linux-gnu] rustflags = ["-Zlinker-features=-lld"] 

Rémy Rakic on behalf of the compiler performance working group

\ Also published here

\ Photo by Antoine Gravier on Unsplash

Market Opportunity
Liberland Logo
Liberland Price(LLD)
$0.806
$0.806$0.806
-6.49%
USD
Liberland (LLD) Live Price Chart
Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.

You May Also Like

Republic Europe Offers Indirect Kraken Stake via SPV

Republic Europe Offers Indirect Kraken Stake via SPV

Republic Europe launches SPV for European retail access to Kraken equity pre-IPO.
Share
bitcoininfonews2026/01/30 13:32
cpwrt Limited Positions Customer Support as a Strategic Growth Function

cpwrt Limited Positions Customer Support as a Strategic Growth Function

For many growing businesses, customer support is often viewed as a cost center rather than a strategic function. cpwrt limited challenges this perception by providing
Share
Techbullion2026/01/30 13:07
Chorus One and MEV Zone Team Up to Boost Avalanche Staking Rewards

Chorus One and MEV Zone Team Up to Boost Avalanche Staking Rewards

The post Chorus One and MEV Zone Team Up to Boost Avalanche Staking Rewards appeared on BitcoinEthereumNews.com. Through the partnership with MEV Zone, Chorus One users will earn extra yield automatically. The Chorus One Avalanche node has a total stake of over 1.7 million, valued at around $55 million. This collaboration will introduce MEV Zone to both public nodes and Validator-as-a-Service. The Avalanche network stands to benefit from fairer and more efficient markets due to enhanced transparency. Chorus One, a highly decorated institutional-grade staking provider, has inked a strategic partnership with MEV Zone to enhance yield generation on the Avalanche (AVAX) network. The Chorus One partnered with MEV Zone to increase the AVAX staking yields, while simultaneously contributing to the general growth of the Avalanche network. “At Chorus One, we see this as an important step in our ongoing journey to provide robust infrastructure and innovative yield strategies for our partners and clients,” the announcement noted.  Why Did Chorus One Partner With MEV Zone? The Chorus One platform has grown to a top-tier institutional-grade staking ecosystem, with more than 40 blockchains, since 2018. In a bid to evolve with the needs of crypto investors and the supported blockchains, Chorus One has inked several strategic partnerships in the recent past, including MEV Zone. In the recent past, MEV Zone has specialized in addressing the Maximal Extractable Value (MEV) challenges on the Avalanche network. The MEV Zone will help Chorus One’s AVAX node validator to use Proposer-Builder Separation (PBS). As such, Chorus One’s AVAX node will seamlessly select certain transactions that are more profitable when making blocks. For instance, MEV Zone will help Chorus One’s AVAX node validator to capture arbitrage and liquidation transactions more often since they are more profitable.  How will Chorus One’s AVAX Stakers Benefit Via This Partnership? The Chorus One AVAX node has grown over the years to more than 1.77 million coins staked, valued…
Share
BitcoinEthereumNews2025/09/18 03:19