public inbox for [email protected]
help / color / mirror / Atom feedFrom: Anthonin Bonnefoy <[email protected]>
To: Thomas Munro <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Segfault in jit tuple deforming on arm64 due to LLVM issue
Date: Fri, 23 Aug 2024 14:22:25 +0200
Message-ID: <CAO6_XqptnQJb52sqpWVAy+9tag3HxQJrP7HEnCso_WZwZCxEgw@mail.gmail.com> (raw)
In-Reply-To: <CA+hUKGLXt-_uSBCBfF=RicvZ4UxGTq_bzKeHSgPJnc6mGPYWbQ@mail.gmail.com>
References: <CAO6_Xqr63qj=Sx7HY6ZiiQ6R_JbX+-p6sTPwDYwTWZjUmjsYBg@mail.gmail.com>
<CA+hUKGLXt-_uSBCBfF=RicvZ4UxGTq_bzKeHSgPJnc6mGPYWbQ@mail.gmail.com>
On Thu, Aug 22, 2024 at 12:33 PM Thomas Munro <[email protected]> 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
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Segfault in jit tuple deforming on arm64 due to LLVM issue
In-Reply-To: <CAO6_XqptnQJb52sqpWVAy+9tag3HxQJrP7HEnCso_WZwZCxEgw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox