←back to thread

Wild – A fast linker for Linux

(github.com)
383 points hkalbasi | 1 comments | 24 Jan 25 16:25 UTC | HN request time: 0s | 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 #
secondcoming ◴[24 Jan 25 17:03 UTC] No.42815102[source]▶
Maybe I'm holding it wrong, but mold isn't faster at all if you're using LTO, which you probably should be.
replies(6): >>42815189 #>>42815221 #>>42815904 #>>42816102 #>>42816403 #>>42840365 #
Arelius ◴[24 Jan 25 19:09 UTC] No.42816102[source]▶
Yeah, if you're development process requires LTO you may be holding it wrong....

Specifically, if LTO is so important that you need to be using it during development, you likely have a very exceptional case, or you have some big architectural issues that are causing much larger performance regressions then they should be.

replies(4): >>42816339 #>>42816648 #>>42823665 #>>42824951 #
1. josephg ◴[25 Jan 25 21:21 UTC] No.42824951{3}[source]▶
> Yeah, if you're development process requires LTO you may be holding it wrong....

I spent a few months doing performance optimisation work. We wanted to see how much performance we could wring out of an algorithm & associated data structures. Each day I’d try and brainstorm new optimisations, implement them, and then A/B test the change to see how it actually affected performance. To get reliable tests, all benchmarks were run in release mode (with all optimisations - including LTO - turned on).