Re: Guiding principle for dropping LLVM versions? - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Guiding principle for dropping LLVM versions?
Date
Msg-id CA+hUKGJy5fz46B5arUE3qQmgCk9myb9np2gh_PpFng1a1Xb71g@mail.gmail.com
Whole thread Raw
In response to Re: Guiding principle for dropping LLVM versions?  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Guiding principle for dropping LLVM versions?
List pgsql-hackers
We could go further.  With LLVM 14 as the minimum we can just use
opaque pointers everywhere, and delete more conditional code in
master.  Tested on 14-18.

I explored using the new pass manager everywhere too.  It almost
worked, but I couldn't see how to override the inlining threshold
before LLVM 16[1], even in C++, so we couldn't fix that with a
llvmjit_wrap.cpp hack.

I like this.  How can I find out if someone would shout at me for
dropping LLVM 13?

[1] https://github.com/llvm/llvm-project/commit/4fa328074efd7eefdbb314b8f6e9f855e443ca20

Attachment

pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: Add the ability to limit the amount of memory that can be allocated to backends.
Next
From: Thomas Munro
Date:
Subject: Re: Remove last traces of HPPA support