Re: Spelling change in LLVM 14 API
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-01-31T05:34:16Z
Lists: pgsql-hackers
Attachments
- v2-0001-Track-LLVM-14-API-changes-2022-01-30.patch (text/x-patch) patch v2-0001
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...
Commits
-
Track LLVM 14 API changes, up to 2022-01-30.
- 807fee1a39de 15.0 landed
-
Track LLVM 14 API changes.
- e6a760020210 15.0 landed