| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Spelling change in LLVM 14 API |
| Date: | 2022-01-31 05:34:16 |
| Message-ID: | CA+hUKG+aGPBkBT5_4czkvzMu6-D+JgPaVL7mX_WBPXgGRndtXA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 26, 2021 at 2:21 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)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 | Content-Type | Size |
|---|---|---|
| v2-0001-Track-LLVM-14-API-changes-2022-01-30.patch | text/x-patch | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2022-01-31 05:46:42 | Re: Latest LLVM breaks our code again |
| Previous Message | Kyotaro Horiguchi | 2022-01-31 05:31:58 | Re: Error "initial slot snapshot too large" in create replication slot |