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

2025/10/05 22:45
Okuma süresi: 4 dk

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

Piyasa Fırsatı
Liberland Logosu
Liberland Fiyatı(LLD)
$0.6
$0.6$0.6
-0.49%
USD
Liberland (LLD) Canlı Fiyat Grafiği
Sorumluluk Reddi: Bu sitede yeniden yayınlanan makaleler, halka açık platformlardan alınmıştır ve yalnızca bilgilendirme amaçlıdır. MEXC'nin görüşlerini yansıtmayabilir. Tüm hakları telif sahiplerine aittir. Herhangi bir içeriğin üçüncü taraf haklarını ihlal ettiğini düşünüyorsanız, kaldırılması için lütfen service@support.mexc.com ile iletişime geçin. MEXC, içeriğin doğruluğu, eksiksizliği veya güncelliği konusunda hiçbir garanti vermez ve sağlanan bilgilere dayalı olarak alınan herhangi bir eylemden sorumlu değildir. İçerik, finansal, yasal veya diğer profesyonel tavsiye niteliğinde değildir ve MEXC tarafından bir tavsiye veya onay olarak değerlendirilmemelidir.

Ayrıca Şunları da Beğenebilirsiniz

The Role of Blockchain in Building Safer Web3 Gaming Ecosystems

The Role of Blockchain in Building Safer Web3 Gaming Ecosystems

The gaming industry is in the midst of a historic shift, driven by the rise of Web3. Unlike traditional games, where developers and publishers control assets and dictate in-game economies, Web3 gaming empowers players with ownership and influence. Built on blockchain technology, these ecosystems are decentralized by design, enabling true digital asset ownership, transparent economies, and a future where players help shape the games they play. However, as Web3 gaming grows, security becomes a focal point. The range of security concerns, from hacking to asset theft to vulnerabilities in smart contracts, is a significant issue that will undermine or erode trust in this ecosystem, limiting or stopping adoption. Blockchain technology could be used to create security processes around secure, transparent, and fair Web3 gaming ecosystems. We will explore how security is increasing within gaming ecosystems, which challenges are being overcome, and what the future of security looks like. Why is Security Important in Web3 Gaming? Web3 gaming differs from traditional gaming in that players engage with both the game and assets with real value attached. Players own in-game assets that exist as tokens or NFTs (Non-Fungible Tokens), and can trade and sell them. These game assets usually represent significant financial value, meaning security failure could represent real monetary loss. In essence, without security, the promises of owning “something” in Web3, decentralized economies within games, and all that comes with the term “fair” gameplay can easily be eroded by fraud, hacking, and exploitation. This is precisely why the uniqueness of blockchain should be emphasized in securing Web3 gaming. How Blockchain Ensures Security in Web3 Gaming?
  1. Immutable Ownership of Assets Blockchain records can be manipulated by anyone. If a player owns a sword, skin, or plot of land as an NFT, it is verifiably in their ownership, and it cannot be altered or deleted by the developer or even hacked. This has created a proven track record of ownership, providing control back to the players, unlike any centralised gaming platform where assets can be revoked.
  2. Decentralized Infrastructure Blockchain networks also have a distributed architecture where game data is stored in a worldwide network of nodes, making them much less susceptible to centralised points of failure and attacks. This decentralised approach makes it exponentially more difficult to hijack systems or even shut off the game’s economy.
  3. Secure Transactions with Cryptography Whether a player buys an NFT or trades their in-game tokens for other items or tokens, the transactions are enforced by cryptographic algorithms, ensuring secure, verifiable, and irreversible transactions and eliminating the risks of double-spending or fraudulent trades.
  4. Smart Contract Automation Smart contracts automate the enforcement of game rules and players’ economic exchanges for the developer, eliminating the need for intermediaries or middlemen, and trust for the developer. For example, if a player completes a quest that promises a reward, the smart contract will execute and distribute what was promised.
  5. Anti-Cheating and Fair Gameplay The naturally transparent nature of blockchain makes it extremely simple for anyone to examine a specific instance of gameplay and verify the economic outcomes from that play. Furthermore, multi-player games that enforce smart contracts on things like loot sharing or win sharing can automate and measure trustlessness and avoid cheating, manipulations, and fraud by developers.
  6. Cross-Platform Security Many Web3 games feature asset interoperability across platforms. This interoperability is made viable by blockchain, which guarantees ownership is maintained whenever assets transition from one game or marketplace to another, thereby offering protection to players who rely on transfers for security against fraud. Key Security Dangers in Web3 Gaming Although blockchain provides sound first principles of security, the Web3 gaming ecosystem is susceptible to threats. Some of the most serious threats include:
Smart Contract Vulnerabilities: Smart contracts that are poorly written or lack auditing will leave openings for exploitation and thereby result in asset loss. Phishing Attacks: Unintentionally exposing or revealing private keys or signing transactions that are not possible to reverse, under the assumption they were genuine transaction requests. Bridge Hacks: Cross-chain bridges, which allow players to move their assets between their respective blockchains, continually face hacks, requiring vigilance from players and developers. Scams and Rug Pulls: Rug pulls occur when a game project raises money and leaves, leaving player assets worthless. Regulatory Ambiguity: Global regulations remain unclear; risks exist for players and developers alike. While blockchain alone won’t resolve every issue, it remediates the responsibility of the first principles, more so when joined by processes such as auditing, education, and the right governance, which can improve their contribution to the security landscapes in game ecosystems. Real Life Examples of Blockchain Security in Web3 Gaming Axie Infinity (Ronin Hack): The Axie Infinity game and several projects suffered one of the biggest hacks thus far on its Ronin bridge; however, it demonstrated the effectiveness of multi-sig security and the effective utilization of decentralization. The industry benefited through learning and reflection, thus, as projects have implemented changes to reduce the risks of future hacks or misappropriation. Immutable X: This Ethereum scaling solution aims to ensure secure NFT transactions for gaming, allowing players to trade an asset without the burden of exorbitant fees and fears of being a victim of fraud. Enjin: Enjin is providing a trusted infrastructure for Web3 games, offering secure NFT creation and transfer while reiterating that ownership and an asset securely belong to the player. These examples indubitably illustrate that despite challenges to overcome, blockchain remains the foundational layer on which to build more secure Web3 gaming environments. Benefits of Blockchain Security for Players and Developers For Players: Confidence in true ownership of assets Transparency in in-game economies Protection against nefarious trades/scams For Developers: More trust between players and the platform Less reliance on centralized infrastructure Ability to attract wealth and players based on provable fairness By incorporating blockchain security within the mechanics of game design, developers can create and enforce resilient ecosystems where players feel reassured in investing time, money, and ownership within virtual worlds. The Future of Secure Web3 Gaming Ecosystems As the wisdom of blockchain technology and industry knowledge improves, the future for secure Web3 gaming looks bright. New growing trends include: Zero-Knowledge Proofs (ZKPs): A new wave of protocols that enable private transactions and secure smart contracts while managing user privacy with an element of transparency. Decentralized Identity Solutions (DID): Helping players control their identities and decrease account theft risks. AI-Enhanced Security: Identifying irregularities in user interactions by sampling pattern anomalies to avert hacks and fraud by time-stamping critical events. Interoperable Security Standards: Allowing secured and seamless asset transfers across blockchains and games. With these innovations, blockchain will not only secure gaming assets but also enhance the overall trust and longevity of Web3 gaming ecosystems. Conclusion Blockchain is more than a buzzword in Web3; it is the only way to host security, fairness, and transparency. With blockchain, players confirm immutable ownership of digital assets, there is a decentralized infrastructure, and finally, it supports smart contracts to automate code that protects players and developers from the challenges of digital economies. The threats, vulnerabilities, and scams that come from smart contracts still persist, but the industry is maturing with better security practices, cross-chain solutions, and increased formal cryptographic tools. In the coming years, blockchain will remain the base to digital economies and drive Web3 gaming environments that allow players to safely own, trade, and enjoy their digital experiences free from fraud and exploitation. While blockchain and gaming alone entertain, we will usher in an era of secure digital worlds where trust complements innovation. The Role of Blockchain in Building Safer Web3 Gaming Ecosystems was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story
Paylaş
Medium2025/09/18 14:40
Knocking Bitcoin's lack of yield shows your ‘Western financial privilege’

Knocking Bitcoin's lack of yield shows your ‘Western financial privilege’

                                                                               Macro analyst Luke Gromen’s comments come amid an ongoing debate over whether Bitcoin or Ether is the more attractive long-term option for traditional investors.                     Macro analyst Luke Gromen says the fact that Bitcoin doesn’t natively earn yield isn’t a weakness; it’s what makes it a safer store of value.“If you’re earning a yield, you are taking a risk,” Gromen told Natalie Brunell on the Coin Stories podcast on Wednesday, responding to a question about critics who dismiss Bitcoin (BTC) because they prefer yield-earning assets.“Anyone who says that is showing their Western financial privilege,” he added.Read more
Paylaş
Coinstats2025/09/18 14:22
Vitalik Buterin wants to build ‘the next generation of finance’ – Here’s how

Vitalik Buterin wants to build ‘the next generation of finance’ – Here’s how

The post Vitalik Buterin wants to build ‘the next generation of finance’ – Here’s how appeared on BitcoinEthereumNews.com. Journalist Posted: February 16, 2026
Paylaş
BitcoinEthereumNews2026/02/16 11:01