Re: upcoming API changes for LLVM 12
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-hackers@postgresql.org
Date: 2020-10-16T20:53:48Z
Lists: pgsql-hackers
Hi, On 2020-10-16 10:22:57 -0400, Tom Lane wrote: > Yeah. As long as we're not breaking the ability to build against older > LLVM, I can't see a reason not to apply and back-patch these changes. > We usually want all supported PG versions to build against newer tool > chains, and this seems to fall into that category. Cool! I just ran that branch against 3.9 (the currently oldest supported version), and that still works. A related question is whether it'd be time to prune the oldest supported LLVM version. 3.9.0 was released 2016-08-31 (and 3.9.1, the only point release, was 2016-12-13). There's currently no *pressing* reason to reduce it, but it is the cause of few #ifdefs - but more importantly it increases the test matrix. I'm inclined to just have a deterministic policy that we apply around release time going forward. E.g. don't support versions that are newer than the newest available LLVM version in the second newest long-term-supported distribution release of RHEL, Ubuntu, Debian? Regards, Andres
Commits
-
backpatch "jit: Add support for LLVM 12."
- 90eb343ef392 11.11 landed
- fa7a52fb9943 12.6 landed
- 6a192c77d21b 13.2 landed
-
jit: Add support for LLVM 12.
- 6c57f2ed16e1 14.0 landed