←back to thread

Wild – A fast linker for Linux

(github.com)
383 points hkalbasi | 3 comments | 24 Jan 25 16:25 UTC | HN request time: 0.602s | source
Show context
pzmarzly ◴[24 Jan 25 16:55 UTC] No.42815005[source]▶
Ever since mold relicensed from AGPL to MIT (as part of mold 2.0 release), the worldwide need for making another fast linker has been greatly reduced, so I wasn't expecting a project like this to appear. And definitely wasn't expecting it to already be 2x faster than mold in some cases. Will keep an eye on this project to see how it evolves, best of luck to the author.
replies(5): >>42815102 #>>42815606 #>>42816517 #>>42819089 #>>42819826 #
estebank ◴[24 Jan 25 17:57 UTC] No.42815606[source]▶
Note that Mold has no interest in becoming incremental, so there is a big reason there for another linker to exist. I find it kind of embarrassing that MS' linker has been incremental by default for decades, yet there's no production ready incremental linker on Linux yet.
replies(4): >>42816198 #>>42817110 #>>42817268 #>>42818469 #
1. pjmlp ◴[24 Jan 25 21:31 UTC] No.42817110[source]▶
Additionally the way precompiled headers are handled in Visual C++ and C++ Builder have always been much better than traditional UNIX compilers, and now we have modules as well.
replies(1): >>42820853 #
2. zik ◴[25 Jan 25 10:48 UTC] No.42820853[source]▶
The way precompiled headers work in C++ is a bit of an ugly hack. And worse, it's almost as slow as just compiling them all every time anyway.
replies(1): >>42820927 #
3. pjmlp ◴[25 Jan 25 11:07 UTC] No.42820927[source]▶
Only in traditional UNIX, which I mentioned.

Borland and Microsoft compilers have been dealing with them just fine since at very least 1994, when I started using Turbo C++ 3.1 for Windows.