Re: Compiler warning on Debian 12, PostgreSQL 16 Beta3

Alvaro Herrera <alvherre@alvh.no-ip.org>

From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: "Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>, Andres Freund <andres@anarazel.de>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2023-11-07T19:13:52Z
Lists: pgsql-hackers
On 2023-Nov-08, Thomas Munro wrote:

> On Wed, Nov 8, 2023 at 4:46 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> > On 2023-Aug-25, Daniel Westermann (DWE) wrote:
> >
> > Yeah, I get this one too.  I thought commit 37d5babb5cfa ("jit: Support
> > opaque pointers in LLVM 16.") was going to silence it, but I was quite
> > mistaken.  I gave that code a quick look and could not understand what
> > it was complaining about.  Is it a bug in the LLVM headers?
> 
> I found the commit where they fixed that in 15+:
> 
> https://github.com/llvm/llvm-project/commit/1d9086bf054c2e734940620d02d4451156b424e6
> 
> They don't seem to back-patch fixes, generally.

Ah yeah, I can silence the warning by patching that file locally.

Annoying :-(

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"El sabio habla porque tiene algo que decir;
el tonto, porque tiene que decir algo" (Platon).



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. jit: Support opaque pointers in LLVM 16.