| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Compiler warning on Debian 12, PostgreSQL 16 Beta3 |
| Date: | 2023-11-07 19:13:52 |
| Message-ID: | 202311071913.tsxjvdsvl4zm@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-Nov-08, Thomas Munro wrote:
> On Wed, Nov 8, 2023 at 4:46 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-11-07 19:55:06 | Re: Add the ability to limit the amount of memory that can be allocated to backends. |
| Previous Message | Thomas Munro | 2023-11-07 18:56:07 | Re: Compiler warning on Debian 12, PostgreSQL 16 Beta3 |