HiPE to be removed in OTP 24?

[Richard O'Keefe]

I am a little puzzled.
Lukas Larsson's recent video
https://www.youtube.com/watch?v=Qz7OCAoiB7Q
presents a long history of Erlang JIT failure
and the new JIT is very new indeed.

I note that in the last quarter of 2019 about
6.4e9 ARM chips were shipped, nearly one for every
person on the planet, in just one quarter.  I
believe about 2/3 of those were for embedded use,
but Erlang should be useful there.  So how long
will it be before the new JIT targets ARM?

The video I linked above talked only about speed,
but for tablet/phone/IoT applications power consumption
is a big issue.  What is known about the new JIT's
effect on power consumption, and are there any plans
to make compiling for low power a consideration in the
JIT design?

On Thu, 18 Jun 2020 at 20: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/20200619/b2126624/attachment.htm>