From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
cc: Michael Paquier <michael@paquier.xyz>, Bruce Momjian <bruce@momjian.us>,
        Sriram RK <sriram.rk@outlook.com>, Andres Freund <andres@anarazel.de>,
        Thomas Munro <thomas.munro@gmail.com>, Noah Misch <noah@leadboat.com>,
        Alvaro Herrera <alvherre@alvh.no-ip.org>,
        "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
        "tvk1271@gmail.com" <tvk1271@gmail.com>,
        Heikki Linnakangas <hlinnaka@iki.fi>
Subject: Re: AIX support
In-reply-to: <d0941d67-04d4-453a-a94d-faf0c1139dca@eisentraut.org>
References: <CA+hUKG+7_ON7hd_oB6YjD4Tx23wL4E1UBSWg6C+O1brMgDB58A@mail.gmail.com> <3847604.1711683217@sss.pgh.pa.us> <CY5PR11MB63921A88005AAE45137A362DFD032@CY5PR11MB6392.namprd11.prod.outlook.com> <20240405172649.d1@rfd.leadboat.com> <CY5PR11MB63921AB0242FAAC1B522DC38FD0E2@CY5PR11MB6392.namprd11.prod.outlook.com> <20240418180128.uzzgx4r6ujgrz2eo@awork3.anarazel.de> <CY5PR11MB6392180DFCCB9A68E5EDE862FD0D2@CY5PR11MB6392.namprd11.prod.outlook.com> <6cc5001e-3001-438a-85fd-3bd2d9c2d8e4@eisentraut.org> <2476719.1713630347@sss.pgh.pa.us> <ZinQeSfk5rOs49ha@momjian.us> <ZinWwJPbIoG9uywQ@paquier.xyz> <3829420.1714018805@sss.pgh.pa.us> <d0941d67-04d4-453a-a94d-faf0c1139dca@eisentraut.org>
Comments: In-reply-to Peter Eisentraut <peter@eisentraut.org>
	message dated "Thu, 25 Apr 2024 10:03:11 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3925361.1714053262.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Apr 2024 09:54:22 -0400
Message-ID: <3925362.1714053262@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3925362.1714053262%40sss.pgh.pa.us>
Precedence: bulk

Peter Eisentraut <peter@eisentraut.org> writes:
> On 25.04.24 06:20, Tom Lane wrote:
>> Something I've been mulling over is whether to suggest that the
>> proposed "new port" should only target building with gcc.

> My understanding is that the old xlc is dead and has been replaced by =

> "xlclang", which is presumably an xlc-compatible frontend on top of =

> clang/llvm.  Hopefully, that will have fewer issues.

[ googles... ]  Actually it seems to be the other way around:
per [1] xlclang is a clang-based front end to IBM's existing
codegen+optimization logic, and the xlc front end is still there too.
It's not at all clear that they have any intention of killing off xlc.

Not sure where that leaves us in terms of either one being an
interesting target to support.  xlclang is presumably an easier lift
to get working, but that also makes it much less interesting from
the preserve-our-portability standpoint.

			regards, tom lane

[1] https://www.ibm.com/docs/en/xl-c-and-cpp-aix/16.1?topic=3Dnew-clang-ba=
sed-front-end