Re: Spelling change in LLVM 14 API - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Spelling change in LLVM 14 API
Date
Msg-id CA+hUKG+aGPBkBT5_4czkvzMu6-D+JgPaVL7mX_WBPXgGRndtXA@mail.gmail.com
Whole thread Raw
In response to Re: Spelling change in LLVM 14 API  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Tue, Oct 26, 2021 at 2:21 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> Here's one like that.  The previous message "Track LLVM 14 API
> changes" didn't seem too scalable so I added date and commit ID.

seawasp finally caught up with these LLVM changes and turned red.  I
retested the patch against this week's LLVM locally.  New version also
adds #include <new>, for the definition of std::new_handler, which g++
is now complaining about in llvmjit_error.cpp.

Since then, the LLVM 14 headers have started spewing deprecation
notices about LLVMBuildStructGEP, LLVMBuildLoad, LLVMBuildCall.  The
warnings say things like "Use LLVMBuildStructGEP2 instead to support
opaque pointers", and the -2 variants need a new argument that takes
an extra LLVMTypeRef argument, but I didn't look further...

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Error "initial slot snapshot too large" in create replication slot
Next
From: Thomas Munro
Date:
Subject: Re: Latest LLVM breaks our code again