From: "H. J. Lu" <hjl@lucon.org>
To: Carsten Langgaard <carstenl@mips.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
linux-mips@fnet.fr, linux-mips@oss.sgi.com,
binutils@sources.redhat.com
Subject: PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC: elf_check_arch() rework)
Date: Thu, 25 Jul 2002 08:26:10 -0700 [thread overview]
Message-ID: <20020725082610.A21614@lucon.org> (raw)
In-Reply-To: <3D3FFD21.8DA26337@mips.com>; from carstenl@mips.com on Thu, Jul 25, 2002 at 03:29:12PM +0200
[-- Attachment #1: Type: text/plain, Size: 3573 bytes --]
I'd like to fix binutils ASAP. Here is a patch.
On Thu, Jul 25, 2002 at 03:29:12PM +0200, Carsten Langgaard wrote:
> "Maciej W. Rozycki" wrote:
>
> > On Wed, 24 Jul 2002, Carsten Langgaard wrote:
> >
> > > We at MIPS are in the process of making an ABI spec for all this, which
> > > is the intention that should be used by the tool-vendors. So please
> > > don't change the ELF header defines.
> >
> > It'd be better the spec matched the real world...
>
> Shouldn't it be the other way around, the real world should follow the spec
> ;-)
> The whole ELF header definition is just one big mess, because we are lacking
> a proper ABI spec.
> That's what has motivated us, to begin making this ABI spec.
>
> We have defined the e_flags this way:
>
> /* 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. */
>
> 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.
> If you look at the elf.h file in glibc, the you will see, it has the same
> values as the kernel.
>
> So I would prefer we fix that in binutils, I guess it not a problem as long
> as you don't have a toolchain that can generate MIPS32 or MIPS64 code.
>
>
> >
> > > I don't see that is wrong with checking the ISA level, I rather have an
> > > error telling me that I can't execute a certain ISA level than
> > > eventually getting a reserved instruction or something worse like
> > > something unpredictable.
> >
> > Well, -ENOEXEC in not any more useful than SIGILL -- with the latter you
> > have at least an idea what happened. The ISA check is not implemented for
> > any Linux port, so there no suitable hook in binfmt_*.c files. You might
> > propose an implementation if that's particularly important for you.
> >
>
> I would like a message telling me that I can't run this ISA level on the
> system.
> Imagined what would happen, if you execute mips3 code and execute ld/sd
> instructions on a mips32 kernel (but on a 64-bit processor), the kernel only
> save half the register and then everything could happen.
>
>
> >
> > > You are obviously right about the elf_check_arch in the 64-bit part of
> > > the kernel is broken. It's probably just be copied from the 32-bit part
> > > without changes, like a lot of the code in the 64-bit kernel is.
> >
> > Possibly, but it still makes me wonder why it wasn't adjusted at the time
> > binfmt_elf32.c was created...
> >
> > Maciej
> >
> > --
> > + Maciej W. Rozycki, Technical University of Gdansk, Poland +
> > +--------------------------------------------------------------+
> > + e-mail: macro@ds2.pg.gda.pl, PGP key available +
>
> --
> _ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
> |\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
> | \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
> TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
> Denmark http://www.mips.com
>
>
>
[-- Attachment #2: elf-mips.patch --]
[-- Type: text/plain, Size: 1023 bytes --]
2002-07-25 H.J. Lu <hjl@gnu.org>
* mips.h (E_MIPS_ARCH_6): New.
(E_MIPS_ARCH_ALGOR_32): New.
(E_MIPS_ARCH_32): Changed.
(E_MIPS_ARCH_64): Changed.
(E_MIPS_ARCH_32R2): New.
(E_MIPS_ARCH_64R2): New.
--- include/elf/mips.h.mips Fri Sep 7 15:43:58 2001
+++ include/elf/mips.h Thu Jul 25 08:21:10 2002
@@ -139,11 +139,23 @@ END_RELOC_NUMBERS (R_MIPS_maxext)
/* -mips5 code. */
#define E_MIPS_ARCH_5 0x40000000
+/* Used by IRIX. */
+#define E_MIPS_ARCH_6 0x50000000
+
+/* Used by Algorithmics. */
+#define E_MIPS_ARCH_ALGOR_32 0x50000000
+
/* -mips32 code. */
-#define E_MIPS_ARCH_32 0x50000000
+#define E_MIPS_ARCH_32 0x60000000
/* -mips64 code. */
-#define E_MIPS_ARCH_64 0x60000000
+#define E_MIPS_ARCH_64 0x70000000
+
+/* MIPS32 code. */
+#define E_MIPS_ARCH_32R2 0x80000000
+
+/* MIPS64 code. */
+#define E_MIPS_ARCH_64R2 0x90000000
/* The ABI of the file. Also see EF_MIPS_ABI2 above. */
#define EF_MIPS_ABI 0x0000F000
next prev parent reply other threads:[~2002-07-25 15:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 17:05 [patch] linux: RFC: elf_check_arch() rework Maciej W. Rozycki
2002-07-24 18:08 ` Daniel Jacobowitz
2002-07-24 19:12 ` Carsten Langgaard
2002-07-24 19:31 ` Daniel Jacobowitz
2002-07-25 11:10 ` Maciej W. Rozycki
2002-07-25 13:29 ` Carsten Langgaard
2002-07-25 14:12 ` Maciej W. Rozycki
2002-07-25 15:26 ` H. J. Lu [this message]
[not found] ` <mailpost.1027610779.9546@news-sj1-1>
2002-07-25 17:49 ` PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC: elf_check_arch() rework) cgd
2002-07-25 18:50 ` David Anderson
2002-07-26 16:53 ` cgd
2002-07-26 17:12 ` Paul Koning
2002-07-29 7:47 ` PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC:elf_check_arch() rework) Carsten Langgaard
2002-07-29 7:47 ` Carsten Langgaard
2002-07-30 14:09 ` Dan Temple
2002-07-30 14:09 ` Dan Temple
2002-07-30 15:07 ` Maciej W. Rozycki
[not found] ` <mailpost.1028038253.3155@news-sj1-1>
2002-07-30 19:20 ` PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC: elf_check_arch() rework) cgd
2002-07-30 19:26 ` Geoff Keating
2002-07-30 19:27 ` cgd
2002-07-30 20:03 ` Eric Christopher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020725082610.A21614@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=carstenl@mips.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox