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-01T03:25:02Z
Lists: pgsql-hackers 
On Wed, Apr 1, 2026 at 12:55 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim@gunduz.org> writes:
> > Fedora pushed 22.1.0 to both Fedora 44 beta and rawhide repos, so I
> > tested these patches. Builds are fine and all regression tests pass.
> > Anything else I should check?
>
> Where are we on getting these patches pushed?  I think the reason that
> BF member midge has been failing of late is that it's running LLVM 22
> (if not indeed something even newer --- configure doesn't report
> the clang version, sadly).  Also, I've reproduced this symptom:

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.

Either way it looks like we need a patch to use alloca instead, which
I'll also look into...

> Intrinsic has incorrect argument type!
> ptr @llvm.lifetime.end.p0
> Intrinsic has incorrect argument type!
> ptr @llvm.lifetime.end.p0
> 2026-03-31 18:58:20.218 EDT [28486] FATAL:  fatal llvm error: Broken module found, compilation aborted!
>
> on a fresh Fedora 44/x86_64 installation with llvm 22.1.1.  So this is
> going to be a production compiler RSN.  (F44 is still labeled beta,
> but not for much longer.)

Yep, that's the issue alright.

Commits

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

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