linux-mips
[Top] [All Lists]

Re: -mcpu vs. binutils 2.13.90.0.18

To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: -mcpu vs. binutils 2.13.90.0.18
From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Date: Wed, 14 May 2003 20:42:56 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <Pine.GSO.3.96.1030514195854.26213L-100000@delta.ds2.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030514175011.GD8833@rembrandt.csv.ica.uni-stuttgart.de> <Pine.GSO.3.96.1030514195854.26213L-100000@delta.ds2.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4i
Maciej W. Rozycki wrote:
[snip]
> > What's desireable here depends on the target system. For Linux,
> > the current way is IMHO the best: o32 only for mips-linux, and
> > o32, n32 and n64 for mips64-linux, with n32 as default.
> 
>  Of course the choice of the default should be configurable (for binutils
> it probably already is

It isn't, and probably will never be. Of course you could introduce
just another configuration, with the bfd vector of your choice as
default.

> -- I recall Richard Sandiford making changes in
> this area, for gcc -- no idea).

It would also need a different config which defines a different
MIPS_DEFAULT_ABI.


Thiemo

<Prev in Thread] Current Thread [Next in Thread>