Re: pgsql: Track LLVM 15 changes.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Track LLVM 15 changes.
Date: 2022-02-15 22:44:40
Message-ID: 3224284.1644965080@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2022-02-16 09:18:53 +1300, Thomas Munro wrote:
>> Yeah I mentioned this problem in the other thread. I got as far as
>> finding this write-up:
>> https://llvm.org/docs/OpaquePointers.html

> Given that major parts of llvm (clang alone contains ~1k references) aren't
> yet transitioned, I wonder if should silence them for now?

For my own part, I don't have any problem with just filtering these
warnings for now. I don't need any buildfarm changes for that.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2022-02-15 22:46:25 Re: pgsql: Ensure that length argument of memcmp() isn't seen as negative.
Previous Message Andres Freund 2022-02-15 22:41:23 Re: pgsql: Track LLVM 15 changes.