HiPE to be removed in OTP 24?

Kenneth Lundin kenneth@REDACTED
Thu Jun 18 12:48:52 CEST 2020

Our plan is to have it ready for product use in OTP 24 (May 2021) for the
x86-64 architecture.

/Kenneth Erlang/OTP, Ericsson

On Thu, Jun 18, 2020 at 12:16 PM Valentin Micic <v@REDACTED> wrote:

> Hi Kenneth,
> Thank you for the information/early warning.
> For what is worth (and FYI):
> We (at Pharos-Avantgard, South Africa) are using HiPE in one of our
> commercial projects (Erlang R21-3)  where we needed a significant
> improvement in performance, and, indeed, HiPE did do the trick.
> This came at the cost, though — we had to refactor our code to avoid
> additional context switching, and hope that new “JIT” (as described by
> Lukas Larsson) will be at least as stable as HiPE now (in Erlang R21-3,
> which is, well, so far so good… and, if you do it “right”).
> When would be the earliest release where “JIT” will be considered fit for
> commercial usage?
> Thanks in advance & kind regards
> V/
> On 18 Jun 2020, at 10:35, Kenneth Lundin <kenneth@REDACTED> 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/20200618/519de6ee/attachment.htm>

More information about the erlang-questions mailing list