Horton

Re: Guiding principle for dropping LLVM versions?

Thomas Munro <thomas.munro@gmail.com>

View thread
From: Thomas Munro <thomas.munro@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org, Xing Guo <higuoxing@gmail.com>, Devrim Gündüz <devrim@gunduz.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-01-25T03:44:43Z
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 →

  1. jit: Require at least LLVM 14, if enabled.

  2. jit: Require at least LLVM 10.

Thanks all for the discussion.  Pushed.  A few build farm animals will
now fail in the configure step as discussed, and need some adjustment
(ie disable LLVM or upgrade to LLVM 10+ for the master branch).

Next year I think we should be able to do a much bigger cleanup, by
moving to LLVM 14+.