At Tue, 30 Jul 2002 14:10:53 +0000 (UTC), "Dan Temple" wrote:
> I've now heard a bit of the history from Nigel at Algorithmics, and
> to summarize, they chose the 6 and 7 values for MIPS32/64 after
> Cygnus, who were also producing a MIPS32/64 toolchain, had chosen
> these. (Algor had originally used the value of 5 for MIPS32, but had
> to changed when both SGI (who assigned it to something else) and
> Cygnus chose otherwise). Hence ARCH_ALGOR_32.
Uh, i believe i've seen a snapshot of the Cygnus MIPS32/64 toolchain
you describe. It was described to me as an "alpha" snapshot. I have
no reason to believe it was ever released as a commercial-quality
I've made an inquiry, and my understanding is that Cygnus/RedHat
internally use the same values as the public tools
(i.e. EF_MIPS_ARCH_MIPS32 == 5, ..._MIPS64 == 6).
> My personal take on this is that the two main commercial providers
> (Cygnus and Algor) of MIPS32/64-capable GNU toolchains have been
> using 6 & 7 for quite a while,
As noted above, at least for Cygnus, I believe this assertion is
> SGI "agree",
with the current master binutils sources. 8-)
As noted in the message:
SGI is using the same values as the master public GNU binutils,
i.e. MIPS32 == 5, MIPS64 == 6. It sounds like it wouldn't hurt them
much to switch, but following your suggestion _would_ involve them
> and that this is quite a
The precedent that I see here is:
* the public master GNU tool sources use EF_MIPS_ARCH_32 == 5,
EF_MIPS_ARCH_64 == 6.
* Cygnus/RedHat uses those same values.
* SGI also uses those same values.
* A fair number of other GNU tool or OS support houses have also
picked up those values and use them.
* Algorithmics uses different values. The meaning of their 'ALGOR_32'
arch value hasn't been mentioned here, I don't know what it is.
But, given that everybody else uses the values that the current GNU
tools do, well, they should probably provide some backward
compatibility for their users if they want it, and switch. (Heck, I
don't even know that 'ALGOR_32' should be different than '32' to
> Hopefully the ABI process will soon shake any other
> issues out too.
Indeed. I look forward to seeing a published ABI proposal.
I strongly encourage you to announce the proposal to other groups than
just the Linux MIPS folks, by the way. For instance, NetBSD is likely
to want to adopt the same ABI for MIPS platforms, and it would be good
if they were able to participate in the process as well. I'd
recommend contacting <firstname.lastname@example.org> (the NetBSD/mips
platform-independent development list), and specifically Simon Burge
<email@example.com> who I believe personally has an interest in
Chris Demetriou Broadcom Corporation
Senior Staff Design Engineer Broadband Processor Business Unit
Any opinions expressed in this message are mine, not necessarily Broadcom's.