HiPE to be removed in OTP 24?

[Grzegorz Junka]

Hi Kenneth,

Thanks to Richard's link I was able to see the presentation about JIT 
and it looks like the team was putting a lot of effort since as early as 
2012 into JIT. But on none of the benchmarks JIT was actually better 
than HiPE.

I am interested, in what way JIT is better than HiPE that it's worth 
putting the effort into developing something new instead of fixing HiPE?

Regards

Grzegorz


On 18/06/2020 08:35, Kenneth Lundin wrote:
>
>
> HiPE is the runtime and compiler support for native code generation of 
> Erlang modules that some of you might have tried, it is part of the 
> OTP repository today.
>
> The OTP team is planning to remove HiPE in the OTP 24 release for the 
> following reasons:
>
>   * we plan to introduce a new way of executing Erlang, the "JIT"
>     described by Lukas Larsson at Code Beam V
>   * since OTP 22, HiPE is not fully functional (does not handle all
>     beam instructions and combinations)
>   * there is no use of HiPE among our primary customers. We actually
>     don't know where HiPE is used except for speeding up Dialyzer
>     which we have another solution for.
>   * The current support for HiPE in the code is a blocker or creates
>     extra work in our new development.
>
> In order to not remove HiPE in OTP 24, we really soon need maintainers 
> committing (long term) to keep HiPE in shape and up to date with the 
> rest of OTP.
>
> /Kenneth Erlang/OTP, Ericsson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20200619/90bcb5ff/attachment.htm>