MIME-Version: 1.0
References: <CAO6_Xqr63qj=Sx7HY6ZiiQ6R_JbX+-p6sTPwDYwTWZjUmjsYBg@mail.gmail.com>
 <CA+hUKGLXt-_uSBCBfF=RicvZ4UxGTq_bzKeHSgPJnc6mGPYWbQ@mail.gmail.com>
In-Reply-To: <CA+hUKGLXt-_uSBCBfF=RicvZ4UxGTq_bzKeHSgPJnc6mGPYWbQ@mail.gmail.com>
From: Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
Date: Fri, 23 Aug 2024 14:22:25 +0200
Message-ID: <CAO6_XqptnQJb52sqpWVAy+9tag3HxQJrP7HEnCso_WZwZCxEgw@mail.gmail.com>
Subject: Re: Segfault in jit tuple deforming on arm64 due to LLVM issue
To: Thomas Munro <thomas.munro@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAO6_XqptnQJb52sqpWVAy%2B9tag3HxQJrP7HEnCso_WZwZCxEgw%40mail.gmail.com>
Precedence: bulk

On Thu, Aug 22, 2024 at 12:33=E2=80=AFPM Thomas Munro <thomas.munro@gmail.c=
om> wrote:
> I fear that back-porting, for the LLVM project, would mean "we fix it
> in main/20.x, and also back-port it to 19.x".  Do distros back-port
> further?

That's also my fear, I'm not familiar with distros back-port policy
but eyeballing ubuntu package changelog[1], it seems to be mostly
build fixes.

Given that there's no visible way to fix the relocation issue, I
wonder if jit shouldn't be disabled for arm64 until either the
RuntimeDyld fix is merged or the switch to JITLink is done. Disabling
jit tuple deforming may be enough but I'm not confident the issue
won't happen in a different part.

[1] https://launchpad.net/ubuntu/+source/llvm-toolchain-16/+changelog