Re: LLVM 22

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 03:20:41
Message-ID: CA+hUKGJFVyQA8QOjB3BSuq9N1VbTvMPzsFG93p=4TmLR8R58zA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 :-)

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

I see a few options, but I need to hack on them for a while to figure
out the tradeoffs, or what I'm missing... after the freeze.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2026-04-02 03:20:59 RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE
Previous Message Tom Lane 2026-04-02 03:18:29 Re: Redundant/mis-use of _(x) gettext macro?