Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qj7UO-009L94-Qj for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Sep 2023 00:24:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qj7UN-004PGt-2a for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Sep 2023 00:24:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qj7UM-004PGY-OC for pgsql-hackers@lists.postgresql.org; Thu, 21 Sep 2023 00:24:14 +0000 Received: from ns5.gunduz.org ([107.170.136.15] helo=ns1.gunduz.org) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qj7UH-005iKZ-2K for pgsql-hackers@lists.postgresql.org; Thu, 21 Sep 2023 00:24:13 +0000 Received: from asus-laptop05.gunduz.org (unknown [140.228.45.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ns1.gunduz.org (Postfix) with ESMTPSA id 45F993FDAA; Thu, 21 Sep 2023 03:24:06 +0300 (+03) Message-ID: <34036e05460e871024873d7542ceff0b2eaac13c.camel@gunduz.org> Subject: Re: LLVM 16 (opaque pointers) From: Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= To: Thomas Munro , PostgreSQL Hackers Cc: Fabien COELHO , Ronan Dunklau , Andres Freund , Dmitry Dolgov <9erthalion6@gmail.com> Date: Thu, 21 Sep 2023 01:24:05 +0100 In-Reply-To: References: <7d82e672-ed84-4fb1-b686-d477a7e2a043@mines-paristech.fr> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Thomas, 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.=C2=A0 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].=C2=A0 Back-patching > further seems a bit harder.=C2=A0 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 :( Regards, --=20 Devrim G=C3=BCnd=C3=BCz Open Source Solution Architect, PostgreSQL Major Contributor Twitter: @DevrimGunduz , @DevrimGunduzTR