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.902
$0.902$0.902
+0.11%
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 [email protected] 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

Institutions Now Control Nearly a Quarter of Available Bitcoin Supply

Institutions Now Control Nearly a Quarter of Available Bitcoin Supply

The post Institutions Now Control Nearly a Quarter of Available Bitcoin Supply appeared on BitcoinEthereumNews.com. Bitcoin 21 September 2025 | 11:00 Fresh figures from BitcoinTreasuries reveal just how concentrated Bitcoin ownership has become among institutions. According to the data, about 3.74 million BTC — nearly 18% of all coins in circulation — are now in the hands of companies, funds, governments, and other organizations. The biggest share belongs to ETFs and publicly listed companies, which have expanded their holdings rapidly since the U.S. approved spot Bitcoin ETFs earlier this year. In total, 332 entities are known to hold reserves: 192 public firms, 44 funds, 68 private companies, 13 governments, 11 DeFi projects, and four major custodians or exchanges. Share of the Available Supply When adjusted for coins that are unlikely to ever move — including the estimated 1.1 million BTC mined by Satoshi Nakamoto and up to 3.7 million that are believed lost — institutional ownership represents closer to 23–25% of the effective supply. Global Distribution The United States leads the pack, with 118 entities reporting Bitcoin reserves. Canada comes next with 43, followed by the UK (21), Japan (12), and Hong Kong (12). Together, these countries dominate the institutional landscape of Bitcoin adoption, both through corporate treasuries and financial products. Growing Influence The sharp increase in institutional ownership coincides with two trends: the arrival of regulated ETFs in major markets and the rise of digital asset treasury firms that manage crypto reserves in the same way corporations handle cash. The shift has accelerated in 2025, further solidifying Bitcoin’s role as a strategic asset in global finance. With nearly a quarter of liquid supply now in institutional hands, Bitcoin’s trajectory is increasingly tied to the strategies of companies, funds, and even governments — raising new questions about how decentralized the ecosystem really is. The information provided in this article is for educational purposes only and…
Share
BitcoinEthereumNews2025/09/21 16:01
XRP bulls brace for key support retest as Bloomberg’s McGlone sounds alarm

XRP bulls brace for key support retest as Bloomberg’s McGlone sounds alarm

XRP hovers on key support as Bloomberg’s McGlone warns of a breakdown while CryptoBull bets on a long consolidation before a major upside breakout. Bloomberg Senior
Share
Crypto.news2026/01/27 18:04
Tourism in Asia is returning, but not in the way it did before

Tourism in Asia is returning, but not in the way it did before

Tourism across Asia is entering a more complex phase. The region is seeing a patchwork of demand shaped by shifting traveler preferences and market segmentation
Share
Bworldonline2026/01/27 16:00