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
