[Top] [All Lists]

Re: -mcpu vs. binutils

To: Thiemo Seufer <>
Subject: Re: -mcpu vs. binutils
From: "Maciej W. Rozycki" <>
Date: Wed, 14 May 2003 20:09:41 +0200 (MET DST)
In-reply-to: <>
Organization: Technical University of Gdansk
Original-recipient: rfc822;
On Wed, 14 May 2003, Thiemo Seufer wrote:

> >  Well, "32" is 32-bit address/data and "64" is 64-bit address/data. 
> > That's essentially pure 32-bit and 64-bit, respectively.  Of course some
> > data format has to be emitted by tools, so there has to be an ABI
> > associated with each of these variants. 
> That's just backwards. An ABI defines much more, e.g. calling
> conventions and GOT sizes. The register size is just another
> property of the ABI.

 OK -- maybe I am biased because there is only a single ABI for 32-bit and
64-bit binaries each.  So please just forget it.

> 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 -- I recall Richard Sandiford making changes in
this area, for gcc -- no idea).

+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+        e-mail:, PGP key available        +

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