Horton

Re: LLVM 22

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Devrim Gündüz <devrim@gunduz.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Matheus Alcantara <matheusssilv97@gmail.com>, Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
Date: 2026-04-02T04:16:14Z
Lists: pgsql-hackers 
On Thu, Apr 2, 2026 at 4:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > On Wed, Apr 1, 2026 at 4:25 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> >> Working on this, more shortly...  I'm trying to figure out if Anthonin
> >> and Andres's feedback means the poison approach does nothing useful
> >> and we might as well just #ifdef out the lifetime.end stuff for LLVM
> > = 22 to fix the breakage today.
>
> > Done.  Hopefully midge and Devrim will now turn green :-)
>
> Just out of curiosity: I see you back-patched that all the way,
> but midge had only been failing on v18 and HEAD.  Were you just
> being defensive, or is there something deeper there?

It was failing locally for me on all branches.

I don't know why midge wasn't failing on 14-17.  Could jit be disabled
somewhere secret?  Aarch64 vs amd64, but this issue doesn't seem to be
architecture related, it's IR-level.

Commits

  1. jit: No backport::SectionMemoryManager for LLVM 22.

  2. jit: Stop emitting lifetime.end for LLVM 22.