3 ms·

There is also an interesting presentation about how Azul implemented their JIT called Falcon, that is fully based on LLVM. https://www.youtube.com/watch?v=Uqch1

There is also an interesting presentation about how Azul implemented their JIT called Falcon, that is fully based on LLVM. https://www.youtube.com/watch?v=Uqch1rjPls8 https://www.youtube.com/watch?v=Uqch1rjPls8 Generally LLVM is a nice idea that allows vendors to reuse major components.

saagarjha 6y ago
The one problem with LLVM is that it’s not very well suited to JIT compilers, a major component of which is its slowness.
- monadic2 6y ago
  That’s not really accurate. It has strict requirements about stack traversal required to appropriately trace memory roots. This is incidental to JIT vs AOT.
  - deleted 6y ago
    [deleted]
  - saagarjha 6y ago
    Did you reply to the wrong comment?
    - monadic2 6y ago
      Sorry, what did you read?
      - saagarjha 6y ago
        This comment: https://news.ycombinator.com/item?id=23744360 https://news.ycombinator.com/item?id=23744360, where you're talking about JIT vs AOT in response to my LLVM one. I couldn't really understand how it followed.
- dougqh2 6y ago
  Former Azul employee here Absolutely correct that LLVM is a fair amount slower than C1 or C2. Azul augmented our JITs with a compilation recording & replay mechanism to combat the general start-up problems posed by JITs (including Falcon). For those who are curious, here's my presentation on the topic: https://2018.jpoint.ru/en/talks/63npsyjpokmukqsag80oia/ https://2018.jpoint.ru/en/talks/63npsyjpokmukqsag80oia/.