Re: Guiding principle for dropping LLVM versions?
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Devrim Gündüz <devrim@gunduz.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-10-18T19:13:56Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
jit: Require at least LLVM 14, if enabled.
- 972c2cd2882b 18.0 landed
-
jit: Require at least LLVM 10.
- 820b5af73dcc 17.0 landed
Attachments
- 0001-jit-Require-at-least-LLVM-14-if-enabled.patch (application/octet-stream) patch 0001
On Thu, Sep 21, 2023 at 12:27 PM Devrim Gündüz <devrim@gunduz.org> wrote: > Even though older LLVM versions exist on both RHEL and Fedora, they > don't provide older Clang packages, which means we have to link to the > latest release anyway (like currently Fedora 38 packages are waiting for > LLVM 16 patch, as they cannot be linked against LLVM 15) That's quite interesting, because it means that RHEL doesn't act as the "lanterne route" for this, ie the most conservative relevant distribution. If we used Debian as a yardstick, PostgreSQL 17 wouldn't need anything older than LLVM 14 AFAICS. Who else do we need to ask? Where could we find this sort of information in machine-readable form (that is feedback I got discussing the wiki page idea with people, ie that it would be bound to become stale and abandoned)? Fresh from doing battle with this stuff, I wanted to see what it would look like if we dropped 3.9...13 in master: 11 files changed, 12 insertions(+), 367 deletions(-) I noticed in passing that the LLVMOrcRegisterJITEventListener configure probes are not present in meson.