Re: LLVM 16 (opaque pointers) - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: LLVM 16 (opaque pointers)
Date
Msg-id CA+hUKGLdgmOGFUEefFGCaofPCsPj4WoCFJ-NpFTMjOFQnaog_w@mail.gmail.com
Whole thread Raw
In response to Re: LLVM 16 (opaque pointers)  (Devrim Gündüz <devrim@gunduz.org>)
Responses Re: LLVM 16 (opaque pointers)
List pgsql-hackers
On Thu, Sep 21, 2023 at 12:24 PM Devrim Gündüz <devrim@gunduz.org> wrote:
> On Thu, 2023-09-21 at 08:22 +1200, Thomas Munro wrote:
> > So far I've tested LLVM versions 10, 15, 16, 17, 18 (= their main
> > branch) against PostgreSQL versions 14, 15, 16.  I've attached the
> > versions that apply to master and 16, and pushed back-patches to 14
> > and 15 to public branches if anyone's interested[1].  Back-patching
> > further seems a bit harder.  I'm quite willing to do it, but ... do we
> > actually need to, ie does anyone really *require* old PostgreSQL
> > release branches to work with new LLVM?
>
> RHEL releases new LLVM version along with their new minor releases every
> 6 month, and we have to build older versions with new LLVM each time.
> From RHEL point of view, it would be great if we can back-patch back to
> v12 :(

Got it.  OK, I'll work on 12 and 13 now.



pgsql-hackers by date:

Previous
From: Devrim Gündüz
Date:
Subject: Re: Guiding principle for dropping LLVM versions?
Next
From: Amit Langote
Date:
Subject: Re: Memory consumed by child SpecialJoinInfo in partitionwise join planning