MIME-Version: 1.0
References: 
 <CA+hUKGJTumad75o8Zao-LFseEbt=enbUFCM7LZVV=c8yg2i7dg@mail.gmail.com>
 <CA+hUKGJv+QUOy8yOHe_0VfRGTSrHaCvo0xZG-1JGTqBurcPkOw@mail.gmail.com>
 <CA+hUKGLJ63fpt_u0OXDR91fbpicDXK01fivzDSBMOtPazEanFQ@mail.gmail.com>
 <afa3914d40d592fc57f50da0d1e99d91f5c8b7dc.camel@gunduz.org>
 <2805479.1775001311@sss.pgh.pa.us>
 <CA+hUKGL1LfD7BTACTx=E78gq_jiFU727osd6tHCnbERrqY8DOA@mail.gmail.com>
 <CA+hUKGJFVyQA8QOjB3BSuq9N1VbTvMPzsFG93p=4TmLR8R58zA@mail.gmail.com>
 <3184815.1775100697@sss.pgh.pa.us>
In-Reply-To: <3184815.1775100697@sss.pgh.pa.us>
From: Thomas Munro <thomas.munro@gmail.com>
Date: Thu, 2 Apr 2026 17:16:14 +1300
Message-ID: 
 <CA+hUKGJ-ktfvRTHeX=DfnS41JjCqPQanOcdY8nhzT0qb5noNzw@mail.gmail.com>
Subject: Re: LLVM 22
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= <devrim@gunduz.org>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
	Matheus Alcantara <matheusssilv97@gmail.com>,
	Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BhUKGJ-ktfvRTHeX%3DDfnS41JjCqPQanOcdY8nhzT0qb5noNzw%40mail.gmail.com>
Precedence: bulk

On Thu, Apr 2, 2026 at 4:31=E2=80=AFPM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > On Wed, Apr 1, 2026 at 4:25=E2=80=AFPM 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
> > =3D 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.