Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: linux-mips@linux-mips.org
Subject: Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA)
Date: Tue, 19 Aug 2003 05:57:56 +0200	[thread overview]
Message-ID: <20030819035756.GC6223@linux-mips.org> (raw)
In-Reply-To: <20030812065118.GD23104@rembrandt.csv.ica.uni-stuttgart.de>

On Tue, Aug 12, 2003 at 08:51:18AM +0200, Thiemo Seufer wrote:

> > 	GCCFLAGS += -mabi=32 -march=mips2 -mtune=r4600 -Wa,--trap
> > (or	GCCFLAGS += $(call check_gcc, -mcpu=r4600 -mips2, -mabi=32 -march=mips2 -mtune=r4600) -Wa,--trap)
> > 
> > Isn't it?
> 
> -march=mips2 is an alias for -march=r6000, I don't think that's a
> good choice.

Why? MIPSII / MIPS32 are the highest ISAs supported for building 32-bit
kernels so that makes sense.

  Ralf

  parent reply	other threads:[~2003-08-19  3:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12  6:26 GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA) Atsushi Nemoto
2003-08-12  6:49 ` Kumba
2003-08-12  7:06   ` Thiemo Seufer
2003-08-12  7:56     ` Kumba
2003-08-12  8:10       ` Thiemo Seufer
2003-08-12  8:26         ` Kumba
2003-08-12  9:25   ` Atsushi Nemoto
2003-08-19  3:52     ` Ralf Baechle
2003-08-12  6:51 ` Thiemo Seufer
2003-08-12 10:06   ` Atsushi Nemoto
2003-08-12 10:16     ` Thiemo Seufer
2003-08-12 15:26       ` Atsushi Nemoto
2003-08-14  3:03         ` Thiemo Seufer
2003-08-12 13:56   ` Maciej W. Rozycki
2003-08-12 14:04     ` Thiemo Seufer
2003-08-12 14:40       ` Maciej W. Rozycki
2003-08-14  3:08         ` Thiemo Seufer
2003-08-19  3:38       ` Ralf Baechle
2003-08-19 12:22         ` Maciej W. Rozycki
2003-08-19 12:34           ` Ralf Baechle
2003-08-19  3:57   ` Ralf Baechle [this message]
2003-08-19  6:41     ` Thiemo Seufer

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=20030819035756.GC6223@linux-mips.org \
    --to=ralf@linux-mips.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