From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
        Peter Geoghegan <pg@bowt.ie>, Andres Freund <andres@anarazel.de>,
        Noah Misch <noah@leadboat.com>, Robert Haas <robertmhaas@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: AIX support - alignment issues
In-reply-to: 
 <CA+hUKGKk7NZO1UnJM0PyixcZPpCGqjBXW_0bzFZpJBGAf84XKg@mail.gmail.com>
References: <20220702183354.a6uhja35wta7agew@alap3.anarazel.de>
 <CAH2-WzndKXQQGh-7sCOTKL_87Kt918r0F2ztTAraeBCAC8v3OQ@mail.gmail.com>
 <968410.1656789743@sss.pgh.pa.us>
 <CAH2-WzmnoGPN--Z7MfTqv2TTVLJF0Y0tzZbGUS-NAwJ0wv15hw@mail.gmail.com>
 <977853.1656794075@sss.pgh.pa.us>
 <CA+hUKGLo8XVq4c=QpXFO5i3t3u5q6Fope=QgRtE-S3RncP+aUg@mail.gmail.com>
 <1415825.1656893299@sss.pgh.pa.us>
 <CA+hUKGJg5kg7LSeKZm1cDFQCTLBWUF1wvuM4eebJBq9DwYfZYw@mail.gmail.com>
 <1827177.1656996797@sss.pgh.pa.us>
 <CA+hUKGJzapRb3UwJF-bLsv=-p6WLk4_hs6WxR8y9LFTSdJBOCw@mail.gmail.com>
 <7890936c-392b-91be-edac-b6d5a500e4b9@enterprisedb.com>
 <CA+hUKGKk7NZO1UnJM0PyixcZPpCGqjBXW_0bzFZpJBGAf84XKg@mail.gmail.com>
Comments: In-reply-to Thomas Munro <thomas.munro@gmail.com>
	message dated "Fri, 08 Jul 2022 14:35:29 +1200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3192763.1657254276.1@sss.pgh.pa.us>
Date: Fri, 08 Jul 2022 00:24:36 -0400
Message-ID: <3192764.1657254276@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3192764.1657254276%40sss.pgh.pa.us>
Precedence: bulk

Thomas Munro <thomas.munro@gmail.com> writes:
> * The documented list mentions some in different endiannesses and word
> sizes explicitly but not others; I think it'd be tidier to list the
> main architecture names and then tack on a "big and little endian, 32
> and 64 bit" sentence.

As phrased, this seems to be saying that we can do both
endiannesses on any of the supported arches, which is a little
weird considering that most of them are single-endianness.  It's
not a big deal, but maybe a tad more word-smithing there would
help?

> * Since Greg Stark's magnificent Vax talk[1], we became even more
> dependent on IEEE 754 via the Ryu algorithm.  AFAICT, unless someone
> produces a software IEEE math implementation for GCC/VAX...  if I had
> a pick one to bump off that list, that's the easiest to argue because
> it definitely doesn't work.

Agreed.  In principle I'd wish that we were not tied to one
floating-point format, but the benefits of Ryu are too hard to
pass up; and reality on the ground is that IEEE 754 achieved
total victory a couple decades ago.  We should stop claiming
that VAX is a realistic target platform.

> What do you think about the attached?

WFM.  Also, that crypt-blowfish.c hunk offers an answer to
your question about whether to worry about "__hppa".

			regards, tom lane