From: Eric Christopher <echristo@redhat.com>
To: cgd@broadcom.com
Cc: dant@mips.com, Carsten Langgaard <carstenl@mips.com>,
hjl@lucon.org, "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
linux-mips@oss.sgi.com, binutils@sources.redhat.com
Subject: Re: PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC: elf_check_arch() rework)
Date: Tue, 30 Jul 2002 13:13:00 -0000 [thread overview]
Message-ID: <1028059433.19879.22.camel@ghostwheel.cygnus.com> (raw)
In-Reply-To: <yov5k7ndkodv.fsf@broadcom.com>
On Tue, 2002-07-30 at 12:27, cgd@broadcom.com wrote:
> At 30 Jul 2002 12:20:57 -0700, Chris G. Demetriou wrote:
> > 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).
>
> Of course, i typo'd most of the names of the constants in my msg. I
> meant E_MIPS_ARCH_32, etc., obviously. 8-)
We have nothing different from what the sources on the net use.
-eric
--
I don't want a pony, I want a rocket
powered jetpack!
prev parent reply other threads:[~2002-07-30 20:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.3.96.1020725125830.27463H-100000@delta.ds2.pg.gda.pl>
[not found] ` <3D3FFD21.8DA26337@mips.com>
2002-07-25 9:17 ` H. J. Lu
[not found] ` <mailpost.1027610779.9546@news-sj1-1>
2002-07-25 11:54 ` cgd
2002-07-25 15:01 ` David Anderson
2002-07-26 9:59 ` cgd
2002-07-26 10:37 ` Paul Koning
2002-07-29 2:22 ` PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC:elf_check_arch() rework) Carsten Langgaard
2002-07-30 8:06 ` Dan Temple
2002-07-30 8:36 ` Maciej W. Rozycki
[not found] ` <mailpost.1028038253.3155@news-sj1-1>
2002-07-30 12:26 ` PATCH: Update E_MIP_ARCH_XXX (Re: [patch] linux: RFC: elf_check_arch() rework) cgd
2002-07-30 12:27 ` Geoff Keating
2002-07-30 13:05 ` cgd
2002-07-30 13:13 ` Eric Christopher [this message]
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=1028059433.19879.22.camel@ghostwheel.cygnus.com \
--to=echristo@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=carstenl@mips.com \
--cc=cgd@broadcom.com \
--cc=dant@mips.com \
--cc=hjl@lucon.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).