Date: Sat, 28 Jan 2023 18:59:37 +0100 From: "Dave Cottlehuber" <dch@FreeBSD.org> To: v@fatpipi.com Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 8893a5541856 - main - lang/elixir-devel: update to 1.14.3 Message-ID: <7f79d820-bf57-4f94-b3c0-2c6ebdae757a@app.fastmail.com> In-Reply-To: <CAB_qb6-aCypHXvm6TLtnABGUVV_Q9rE0dgo5BX89ZAfFda=UHA@mail.gmail.com> References: <202301251942.30PJgbGg048332@gitrepo.freebsd.org> <CAB_qb6-aCypHXvm6TLtnABGUVV_Q9rE0dgo5BX89ZAfFda=UHA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 28 Jan 2023, at 03:50, Vanilla Hsu wrote: > How about changing the default ERLANG_VER to 25 with elixir-devel's Ma= kefile? > > it's 24 now. Hi Vanilla, This only impacts the *compiler* used to build Elixir, not the *runtime*= one. If we build with 25, then it can't be used against a runtime 24 anymore. In practice there should be no runtime performance difference between an OTP24-compiled Elixir, and an OTP25-compiled Elixir, when running OTP25 Elixir code. We have had a few years where the OTP release bytecode hasn't changed, b= ut this will change for OTP26: - https://www.erlang.org/doc/general_info/deprecations.html - https://www.erlang.org/doc/general_info/upcoming_incompatibilities.html If you build llvm15 from llvm14 or llvm13, and then build C code using llvm15, do you get different results? I'm curious to know if this is the case! In a month or two (before 2023Q2 branches, we should switch all the lang/erlang ports over to OTP25 which will be the new "default", and add OTP26. Mid May, I think. Once net/rabbitmq is switched over to use the generic UNIX tarball, instead of the current somewhat bespoke build, we can keep lang/elixir up to date much faster. A+ Dave =E2=80=94 O for a muse of fire, that would ascend the brightest heaven of inventio= n!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7f79d820-bf57-4f94-b3c0-2c6ebdae757a>