MIME-Version: 1.0
References: <CA+hUKGKNX_=f+1C4r06WETKTq0G4Z_7q4L4Fxn5WWpMycDj9Fw@mail.gmail.com>
 <CA+hUKG+WXznXCyTgCADd=HWkP9Qksa6chd7L=GCnZo-MBgg9Lg@mail.gmail.com>
 <7d82e672-ed84-4fb1-b686-d477a7e2a043@mines-paristech.fr> <CA+hUKG+UQq_qZWuAd8Mv=RpL4sACEb=4UNgNL2--=xZHixVspg@mail.gmail.com>
 <34036e05460e871024873d7542ceff0b2eaac13c.camel@gunduz.org>
In-Reply-To: <34036e05460e871024873d7542ceff0b2eaac13c.camel@gunduz.org>
From: Thomas Munro <thomas.munro@gmail.com>
Date: Thu, 21 Sep 2023 12:47:35 +1200
Message-ID: <CA+hUKGLdgmOGFUEefFGCaofPCsPj4WoCFJ-NpFTMjOFQnaog_w@mail.gmail.com>
Subject: Re: LLVM 16 (opaque pointers)
To: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= <devrim@gunduz.org>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Fabien COELHO <coelho@cri.ensmp.fr>, 
	Ronan Dunklau <ronan.dunklau@aiven.io>, Andres Freund <andres@anarazel.de>, 
	Dmitry Dolgov <9erthalion6@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BhUKGLdgmOGFUEefFGCaofPCsPj4WoCFJ-NpFTMjOFQnaog_w%40mail.gmail.com>
Precedence: bulk

On Thu, Sep 21, 2023 at 12:24=E2=80=AFPM Devrim G=C3=BCnd=C3=BCz <devrim@gu=
nduz.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 (=3D 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.