Comment by zerr 15 hours ago But it doesn't have neither AOT nor JIT. 4 comments zerr Reply arcanemachiner 15 hours ago I believe BEAM bytecode is now JIT-ed.EDIT: It is, since OTP 24 was released in 2021:https://www.erlang.org/downloads/24> The BeamAsm JIT-compiler has been added to Erlang/OTP and will give a significant performance boost for many applications. The JIT-compiler is enabled by default on most x86 64-bit platforms that have a C++ compiler that can compile C++17. foxes 15 hours ago elixir/erlang gets compiled into beam byte code. It's a vm. why does this matter.. zerr 13 hours ago It's an interpreted byte code run (interpreted) by BEAM. Not a native binary run by CPU.But apparently BeamAsm JIT solves the issue? As mentioned in the sibling comment. conradfr 15 hours ago What about https://www.erlang.org/doc/apps/erts/beamasm.html
arcanemachiner 15 hours ago I believe BEAM bytecode is now JIT-ed.EDIT: It is, since OTP 24 was released in 2021:https://www.erlang.org/downloads/24> The BeamAsm JIT-compiler has been added to Erlang/OTP and will give a significant performance boost for many applications. The JIT-compiler is enabled by default on most x86 64-bit platforms that have a C++ compiler that can compile C++17.
foxes 15 hours ago elixir/erlang gets compiled into beam byte code. It's a vm. why does this matter.. zerr 13 hours ago It's an interpreted byte code run (interpreted) by BEAM. Not a native binary run by CPU.But apparently BeamAsm JIT solves the issue? As mentioned in the sibling comment.
zerr 13 hours ago It's an interpreted byte code run (interpreted) by BEAM. Not a native binary run by CPU.But apparently BeamAsm JIT solves the issue? As mentioned in the sibling comment.
I believe BEAM bytecode is now JIT-ed.
EDIT: It is, since OTP 24 was released in 2021:
https://www.erlang.org/downloads/24
> The BeamAsm JIT-compiler has been added to Erlang/OTP and will give a significant performance boost for many applications. The JIT-compiler is enabled by default on most x86 64-bit platforms that have a C++ compiler that can compile C++17.
elixir/erlang gets compiled into beam byte code. It's a vm. why does this matter..
It's an interpreted byte code run (interpreted) by BEAM. Not a native binary run by CPU.
But apparently BeamAsm JIT solves the issue? As mentioned in the sibling comment.
What about https://www.erlang.org/doc/apps/erts/beamasm.html