Re: Guiding principle for dropping LLVM versions?

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Devrim Gündüz <devrim(at)gunduz(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Guiding principle for dropping LLVM versions?
Date: 2023-10-20 02:36:21
Message-ID: CA+hUKGJy5fz46B5arUE3qQmgCk9myb9np2gh_PpFng1a1Xb71g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
v2-0001-jit-Require-at-least-LLVM-14-if-enabled.patch text/x-patch 27.8 KB
v2-0002-jit-Use-opaque-pointers-in-all-supported-LLVM-ver.patch text/x-patch 7.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-10-20 02:44:31 Re: Remove last traces of HPPA support
Previous Message Andrei Lepikhov 2023-10-20 02:36:07 Re: Add the ability to limit the amount of memory that can be allocated to backends.