public inbox for [email protected]  

help / color / mirror / Atom feed

From: Thomas Munro <[email protected]>
To: Tom Lane <[email protected]>
Cc: Devrim Gündüz <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Matheus Alcantara <[email protected]>
Cc: Anthonin Bonnefoy <[email protected]>
Subject: Re: LLVM 22
Date: Wed, 1 Apr 2026 16:25:02 +1300
Message-ID: <CA+hUKGL1LfD7BTACTx=E78gq_jiFU727osd6tHCnbERrqY8DOA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CA+hUKGJTumad75o8Zao-LFseEbt=enbUFCM7LZVV=c8yg2i7dg@mail.gmail.com>
	<CA+hUKGJv+QUOy8yOHe_0VfRGTSrHaCvo0xZG-1JGTqBurcPkOw@mail.gmail.com>
	<CA+hUKGLJ63fpt_u0OXDR91fbpicDXK01fivzDSBMOtPazEanFQ@mail.gmail.com>
	<[email protected]>
	<[email protected]>

On Wed, Apr 1, 2026 at 12:55 PM Tom Lane <[email protected]> wrote:
> Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <[email protected]> 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.

view thread (15+ 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], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: LLVM 22
  In-Reply-To: <CA+hUKGL1LfD7BTACTx=E78gq_jiFU727osd6tHCnbERrqY8DOA@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