3 ms·

I think the parent poster is saying that LLD needs to take a different approach, not Zig. But it wasn't previously known what approach that would need to be, si

by shawnz 6y ago

I think the parent poster is saying that LLD needs to take a different approach, not Zig. But it wasn't previously known what approach that would need to be, since M1 does it differently than other ARM CPUs. Therefore there's no expectation that LLD could have gotten it right.

refulgentis 6y ago
LLVM/Clang were essentially born and stewarded by Apple, it's somewhat odd, to say the least, that they didn't patch LLD on day 1 with the Xcode release that supports M1.
- ndesaulniers 6y ago
  This assumes that LLD has been around much longer than it has. Apple first sponsored development of LLVM, before clang or LLD existed. Then they sponsored clang development. LLD came much later. I believe Rui created LLD at Google with an intention of linking Chrome on Windows. That was a very different use case than what Apple had in mind. Eventually LLD abstracted the target object file, could link ELF executables, and had a good design for furthering support for mach-o. Facebook is developing that in LLD surely to support linking their iOS app much faster. Apple remains disinterested from what I can tell.
  - refulgentis 6y ago
    thank you, learned a lot :) (I had assumed lld came with the llvm/clang switchover back in...ios 5?)