linux-mips
[Top] [All Lists]

Re: -mcpu vs. binutils 2.13.90.0.18

To: linux-mips@linux-mips.org
Subject: Re: -mcpu vs. binutils 2.13.90.0.18
From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Date: Tue, 13 May 2003 21:27:35 +0200
Cc: Guido Guenther <agx@sigxcpu.org>
In-reply-to: <20030513113316.GU3889@bogon.ms20.nix>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030318154155.GF2613@bogon.ms20.nix> <20030318160303.GN13122@rembrandt.csv.ica.uni-stuttgart.de> <20030318174241.GG2613@bogon.ms20.nix> <20030318190841.GO13122@rembrandt.csv.ica.uni-stuttgart.de> <20030318232454.GA19990@bogon.ms20.nix> <20030319001652.GB19189@rembrandt.csv.ica.uni-stuttgart.de> <20030513113316.GU3889@bogon.ms20.nix>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4i
Guido Guenther wrote:
[snip]
> > > So to build kernels for say IP22 R5k I'd change the current
> > >   GCCFLAGS += -mcpu=r5000 -mips2 -Wa,--trap
> > > to 
> > >   GCCFLAGS += -mabi=o32 -march=R5000 -mtune=R5000 -Wa,--trap
> > > where as for R4X00 I use
> > >   GCCFLAGS += -mabi=o32 -march=R4600 -mtune=R4600 -Wa,--trap
> > > Correct?
> > 
> > Yes, this should work. You can leave the -mtune out, since it defaults
> > to the value of -march anyway.
> Just for completeness: I had to use:
>       GCCFLAGS += -mabi=32 -march=r4600 -mtune=r4600 -Wa,--trap
> to make gcc-3.3 happy (note the 32 instead of o32).

Yes, IIRC 64 vs. n64 has the same problem.

> gcc-3.2 doesn't seem
> to handle these options correctly at all.

AFAICS you can still drop the -mtune part.


Thiemo

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