| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Devrim Gündüz <devrim(at)gunduz(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
| Subject: | Re: LLVM 22 |
| Date: | 2026-04-02 04:16:14 |
| Message-ID: | CA+hUKGJ-ktfvRTHeX=DfnS41JjCqPQanOcdY8nhzT0qb5noNzw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 2, 2026 at 4:31 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > On Wed, Apr 1, 2026 at 4:25 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Fittl | 2026-04-02 04:17:35 | Re: pg_test_timing: fix unit typo and widen diff type |
| Previous Message | Chao Li | 2026-04-02 04:15:48 | Re: Check some unchecked fclose() results |