Re: LLVM 22 - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: LLVM 22
Date
Msg-id CA+hUKGJ-ktfvRTHeX=DfnS41JjCqPQanOcdY8nhzT0qb5noNzw@mail.gmail.com
Whole thread
In response to Re: LLVM 22  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: LLVM 22
List 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.



pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Check some unchecked fclose() results
Next
From: Lukas Fittl
Date:
Subject: Re: pg_test_timing: fix unit typo and widen diff type