Re: Where are we on supporting LLVM's opaque-pointer changes?

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Where are we on supporting LLVM's opaque-pointer changes?
Date: 2023-04-16 01:00:36
Message-ID: CA+hUKGLXK6fWdL3hitdc8ksmSLyk5wNA57HLO5FTyzE8iRpQ=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Apr 15, 2023 at 2:31 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I know we've been letting this topic slide, but we are out of runway.
> I propose adding this as a must-fix open item for PG 16.

I had a patch that solved many of the problems[1], but it isn't all
the way there and I got stuck. I am going to look at it together with
Andres in the next couple of days, get unstuck, and aim to get a patch
out this week. More soon.

[1] https://github.com/macdice/postgres/tree/llvm15

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2023-04-16 04:28:13 idea: multiple arguments to_regclass function
Previous Message Peter Geoghegan 2023-04-16 00:15:11 Re: segfault tied to "IS JSON predicate" commit