This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC:elf_check_arch() rework)
- From: cgd at broadcom dot com
- To: hjl at lucon dot org
- Cc: "Carsten Langgaard" <carstenl at mips dot com>,"Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>,linux-mips at fnet dot fr,linux-mips at oss dot sgi dot com,binutils at sources dot redhat dot com,davea at quasar dot engr dot sgi dot com
- Date: 25 Jul 2002 10:49:30 -0700
- Subject: Re: PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC:elf_check_arch() rework)
- References: <Pine.GSO.3.96.1020725125830.27463H-100000@delta.ds2.pg.gda.pl><3D3FFD21.8DA26337@mips.com> <20020725082610.A21614@lucon.org><mailpost.1027610779.9546@news-sj1-1>
[ Added David Anderson (hopefully still 8-) @ SGI to the CC list,
since he's been helpful with sorting out questions like this in the
past.
At Thu, 25 Jul 2002 15:26:19 +0000 (UTC), "H. J. Lu" wrote:
> I'd like to fix binutils ASAP. Here is a patch.
People using stock binutils have been using the current binutils MIPS
arch values for a While now. They were in 2.11.1 and later binutils
releases, as well.
> > /* ELF header e_flags defines. MIPS architecture level. */
> > #define EF_MIPS_ARCH_1 0x00000000 /* -mips1 code. */
> > #define EF_MIPS_ARCH_2 0x10000000 /* -mips2 code. */
> > #define EF_MIPS_ARCH_3 0x20000000 /* -mips3 code. */
> > #define EF_MIPS_ARCH_4 0x30000000 /* -mips4 code. */
> > #define EF_MIPS_ARCH_5 0x40000000 /* -mips5 code. */
> > #define EF_MIPS_ARCH_32 0x60000000 /* MIPS32 code. */
> > #define EF_MIPS_ARCH_64 0x70000000 /* MIPS64 code. */
> > #define EF_MIPS_ARCH_32R2 0x80000000 /* MIPS32 code. */
> > #define EF_MIPS_ARCH_64R2 0x90000000 /* MIPS64 code. */
Why are 2 definitions of MIPS32 and MIPS64 needed?
Certainly, if you do need different definitions, they need much better
comments than that.
> > The missing value 0x50000000, is because IRIX has defined a EF_MIPS_ARCH_6
> > and Algorithmics has a E_MIPS_ARCH_ALGOR_32, which has this value.
It's unfortunate that MIPS is only at this late stage getting into the
business of defining these fields.
Has IRIX actually _used_ EF_MIPS_ARCH_6 for anything (shipped)? That
i'm a bit concerned about, since interoperability with IRIX would be a
good thing given that SGI has been setting the only ABI example to
follow for MIPS.
Algorithmics may have done something different, but they have also
been capable of contributing their binutils-related changes back to
the binutils projects, yet they have not. Why muck things up for
people who _have_, or who've been using the tools, on their account?
cgd
--
Chris Demetriou Broadcom Corporation
Senior Staff Design Engineer Broadband Processor Business Unit
Any opinions expressed in this message are mine, not necessarily Broadcom's.