From: Daniel Jacobowitz <dan@debian.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: linux-mips@linux-mips.org, Guido Guenther <agx@sigxcpu.org>
Subject: Re: -mcpu vs. binutils 2.13.90.0.18
Date: Tue, 13 May 2003 15:36:25 -0400 [thread overview]
Message-ID: <20030513193625.GA14066@nevyn.them.org> (raw)
In-Reply-To: <20030513192735.GA16497@rembrandt.csv.ica.uni-stuttgart.de>
On Tue, May 13, 2003 at 09:27:35PM +0200, Thiemo Seufer wrote:
> 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.
That's not quite the same: 64 is o64, n64 is n64. GCC's never called
the 32-bit ABI "o32".
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-13 19:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 15:41 -mcpu vs. binutils 2.13.90.0.18 Guido Guenther
2003-03-18 16:03 ` Thiemo Seufer
2003-03-18 17:42 ` Guido Guenther
2003-03-18 19:08 ` Thiemo Seufer
2003-03-18 23:24 ` Guido Guenther
2003-03-19 0:16 ` Thiemo Seufer
2003-03-19 1:25 ` Guido Guenther
2003-05-13 11:33 ` Guido Guenther
2003-05-13 19:27 ` Thiemo Seufer
2003-05-13 19:36 ` Daniel Jacobowitz [this message]
2003-05-13 19:59 ` Thiemo Seufer
2003-05-15 3:55 ` Daniel Jacobowitz
2003-05-13 20:11 ` Guido Guenther
2003-05-13 20:50 ` Thiemo Seufer
2003-05-13 22:22 ` Guido Guenther
2003-05-14 10:53 ` Maciej W. Rozycki
2003-05-14 15:12 ` Thiemo Seufer
2003-05-14 17:03 ` Maciej W. Rozycki
2003-05-14 17:50 ` Thiemo Seufer
2003-05-14 18:09 ` Maciej W. Rozycki
2003-05-14 18:42 ` Thiemo Seufer
2003-05-15 11:39 ` Maciej W. Rozycki
2003-05-15 11:50 ` Thiemo Seufer
2003-05-15 12:38 ` Maciej W. Rozycki
2003-03-26 16:05 ` Maciej W. Rozycki
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=20030513193625.GA14066@nevyn.them.org \
--to=dan@debian.org \
--cc=agx@sigxcpu.org \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@linux-mips.org \
/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