HN Explorer

19 comments

[ 2.3 ms ] story [ 59.0 ms ] thread
hongbo_zhang
MoonBit supports the LLVM backend. With this, it achieved 8× Java’s performance in FFT and introduced out-of-the-box debugging with DWARF symbol injection, enabling precise source mapping directly to compiled outputs.

MoonBit will soon compile directly to native binary files without relying on a C compiler. This eliminates various compatibility issues associated with C compilers.

code_mary22
Does this mean MoonBit will get JIT support soon?
hongbo_zhang
we have a interpreter mode which takes advantage of tcc for fast interpretion
ftbsqcfjm
"The LLVM backend seems like a natural fit for MoonBit, but I wonder how it handles complex optimizations like inlining and dead code elimination. Has anyone benchmarked it against other LLVM-based languages?"
tech_peter01
Wonder how the LLVM backend affects compile times. Anyone tried it yet?
hongbo_zhang
it is not the optimial, for fast native mode, we rely on tcc for fast interpretion
techblaze3
I assume there was a C backend before — some numbers comparing that and the wasm backend with LLVM would’ve been helpful."
hongbo_zhang
The LLVM mode currently is not good as C backend, but we are working on it to bring it comparable to C backend
kukiTsui
It's great to see MoonBit adopt llvm, but is it relying on a c compiler or independent?
TitanShift
"Once support for distributing precompiled runtime libraries is implemented, MoonBit programs will be completely independent of the C compiler, generating native executables using only a linker."
hongbo_zhang
we used to output C for native backend support
[deleted]
(comment deleted)
k_8HjR2mN5
Fun to see more languages taking advantage of LLVM. Opens up a lot of potential.