public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
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 08:34:00 -0000	[thread overview]
Message-ID: <20050223005736.GH7729@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <1109117126.5032.51.camel@localhost.localdomain>

Eric Christopher wrote:
> 
> > 
> > It is not a guess in this case, and gcc uses the from-abi hack to
> > figure it out correctly. Without it, e.g.
> > 
> > 	gcc -mabi=64
> > 
> > would behave differently depending on its configuration. That's surely
> > counterintuitive and adds e.g. more breakage potential to Makefile
> > portability.
> 
> As long as the arch is passed along as 'from-abi' I'm ok with changing
> it.

from-abi is always mips3 for NewABI.

> The problem with allowing people to just put -mabi=64 on a, say,
> mips-linux-gnu compiler is that they may expect it's giving them, say,
> mips4 code (I've heard it) and not mips3 code as you'd want to make it.

Mips4 is the default for the native IRIX ABI64 toolchain, gcc on IRIX
defaults to mips3 for ABI64, like Linux does. That's probably the
source of confusion here.

> Having it error and make people be specific is the best bet I think, or
> "from-abi" - at least that way they know that they're getting what we
> choose :)

They already specified it with -mabi, as mips3 is the minimum required
for NewABI.


Thiemo

  reply	other threads:[~2005-02-23  0:57 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 [this message]
2005-02-23  9:38               ` Eric Christopher
2005-02-23  9:47                 ` Thiemo Seufer
2005-02-23  9:57                   ` Thiemo Seufer
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=20050223005736.GH7729@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).