Live data from Hacker News

The LLVM Compiler Infrastructure

cacm.acm.org

21–23 of 23 posts

Re: The LLVM Compiler Infrastructure

#21
post #7

This infrastructure is also slow and leads to poor compilation times for any language that uses llvm as a backend. In an era of automatic code generation, this will become more and more of a problem as llvm compilation times will become a huge bottleneck. I am very bearish on llvm as a technology and while I will acknowledge its influence, I expect that it is at or near its peak and market share will decline dramatic…

> leads to poor compilation times for any language that uses llvm as a backend

it doesn't take long for user delay to sum to more than developer delay

Re: The LLVM Compiler Infrastructure

#22

Earlier quoted context omitted.

Is there a URL for that language? It is unfortunately a bit un-googleable!

found this: https://logicaffeine.com/guide

Yes that's the language, the v0.10.0 benchmarks are coming very soon and with it some major updates. We've added supercompilation and symmetry breaking to the optimizer pipeline. Sneak peeks available on a branch currently named stream1. https://github.com/Brahmastra-Labs/logicaffeine/tree/stream1

Re: The LLVM Compiler Infrastructure

#23
post #7

This infrastructure is also slow and leads to poor compilation times for any language that uses llvm as a backend. In an era of automatic code generation, this will become more and more of a problem as llvm compilation times will become a huge bottleneck. I am very bearish on llvm as a technology and while I will acknowledge its influence, I expect that it is at or near its peak and market share will decline dramatic…

It makes perfect sense to ditch LLVM in development contexts, as its slowness is antithetical to developer productivity — most obviously in tight edit-compile-test loops. And this becomes orders of magnitude more salient when the edit-compile-test loop is being driven by AI. But even when languages are described as "moving away" that usually means building their own very fast-compiling/min-optimising x64/ARM backend…

For developer productivity, you can move to a REPL workflow with edit-compile-test at the function level. Julia does this while staying on LLVM.

Of course, compile-the-world is still going to be slow, but there is no solution for that in the C++/Rust ecosystems either.

Post reply on HN