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: 2021-09-24T00:52:09Z
Lists: pgsql-hackers
Attachments
- 0001-Track-LLVM-14-API-changes.patch (text/x-patch) patch 0001
On Mon, Aug 30, 2021 at 5:41 AM Andres Freund <andres@anarazel.de> wrote: > - if (F.getAttributes().hasFnAttribute(llvm::Attribute::NoInline)) > + if (F.getAttributes().hasAttribute(llvm::Attribute::FunctionIndex, llvm::Attribute::NoInline)) Yeah, that's already stopped working since you wrote it a few weeks ago... There's also been a second breakage site in our code due to LLVM commit 85b732b5. New fix attached. Tested on LLVM 7, 9, 13, 14 (= LLVM main branch commit 945df8bc4cf3 built 2021-09-15). Even though the macro approach is ugly, we're already handling every other API change that way, and at least it's at least very clear which lines to delete in a few years when older LLVMs fall off the conveyor belt of time. Admittedly renaming an identifiers is a new kludge, but I didn't want to duplicate the whole if block or confuse pgindent.
Commits
-
Track LLVM 14 API changes, up to 2022-01-30.
- 807fee1a39de 15.0 landed
-
Track LLVM 14 API changes.
- e6a760020210 15.0 landed