> Modular found ways to parralize LLVM code generation by introducing novel techniques
replyWhat techniques?
I think they had a good dive here
https://www.youtube.com/watch?v=SEwTjZvy8vw
The gist is that MLIR (unlike LLVM) was designed to be multithreaded so the whole stack above LLVM IR is parallel, and then LLVM is used as a per-function codegen tool in parallel, so although LLVM itself is single threaded there are multiple seperate contexts of it. also I think they wrote their own linker.
replyThat is hardly novel, here is the thesis for the Oberon multithreaded compiler from 2003.
replyhttps://www.research-collection.ethz.ch/entities/publication...
C# compiler is also fully multithreaded since the Roslyn rewrite in 2016.
The novelty is in parrelizing LLVM, which is traditionally a single-thread code generator.
replySo basically LLVM catching up with times.
replyFrom experience, Zig compile times are at least as fast as Go for debug builds that don't need to do linking with C libraries, etc. It does have to use LLVM for release builds however which is a lot slower.
replyMojo compiles with O2 by default, it is similar to Go here. Release build is the default, debug is something you opt into. It is still very fast nonetheless
reply