From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: Eric Christopher <echristo@redhat.com>
Cc: "Maciej W. Rozycki" <macro@mips.com>,
binutils@sources.redhat.com,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] MIPS gas/ld test suite portability fixes
Date: Wed, 23 Feb 2005 09:57:00 -0000 [thread overview]
Message-ID: <20050223032531.GJ7729@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <20050223022601.GI7729@rembrandt.csv.ica.uni-stuttgart.de>
Thiemo Seufer wrote:
[snip]
> > Right, I meant as long as they do this:
> >
> > gas -march=from-abi -mabi=64
> >
> > just as they would with a gcc that wasn't configured for the right
> > abi/isa.
>
> Gcc does not behave that way for mips{,64}-linux, see MIPS_ISA_DEFAULT
> and MIPS_CPU_STRING_DEFAULT. If neither is defined, the arch will be
> figured out from the ABI. It would IMHO make no sense to fail on
> "mips-linux-gcc -mabi=64" just because there's no arch specified.
>
> mipsisa32*-linux fails because it defines MIPS_ISA_DEFAULT instead
> of MIPS_CPU_STRING_DEFAULT.
>
> Most of the mips*-elf targets define MIPS_ISA_DEFAULT, some define
> additionally MIPS_CPU_STRING_DEFAULT.
>
> Those gcc configurations should probably be changed to define
> MIPS_CPU_STRING_DEFAULT only, with the ISA-generic default cpu value
> for an ISA-specific config.
This of course wouldn't change anything for the problem discussed
here, bacause any of both defines is enough to override the from-abi
selection. It would only avoid to have a (partial) duplicate ISA/CPU
table in the configuration script.
In the end we have two different approaches for ISA/ARCH selection,
a CPU-centric and an ABI-centric one. For the latter we want to have
sensible ISA defaults. This should be ok as long as we don't interfere
with the CPU-centric usage, which means elevating the ISA level to
the ABI requirement can be done, but lowering it from a higher level
can't.
Thiemo
next prev parent reply other threads:[~2005-02-23 3:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 19:24 Maciej W. Rozycki
2005-02-22 20:21 ` Daniel Jacobowitz
2005-02-22 21:15 ` Maciej W. Rozycki
2005-02-22 21:24 ` Daniel Jacobowitz
2005-02-22 23:38 ` Thiemo Seufer
2005-02-22 23:53 ` Maciej W. Rozycki
2005-02-23 0:05 ` Thiemo Seufer
2005-02-23 0:06 ` Eric Christopher
2005-02-23 0:57 ` Thiemo Seufer
2005-02-23 8:32 ` Eric Christopher
2005-02-23 8:34 ` Thiemo Seufer
2005-02-23 9:38 ` Eric Christopher
2005-02-23 9:47 ` Thiemo Seufer
2005-02-23 9:57 ` Thiemo Seufer [this message]
2005-02-23 14:26 ` Richard Sandiford
2005-02-23 16:39 ` Thiemo Seufer
2005-02-23 17:05 ` Richard Sandiford
2005-02-23 19:22 ` Maciej W. Rozycki
2005-02-24 1:47 ` Thiemo Seufer
2005-02-24 15:53 ` Richard Sandiford
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=20050223032531.GJ7729@rembrandt.csv.ica.uni-stuttgart.de \
--to=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=macro@linux-mips.org \
--cc=macro@mips.com \
/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).