Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Dimitri Torfs <dimitri@sonycom.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-mips@linux-mips.org
Subject: Re: Support for newer gcc/gas options
Date: Sat, 10 Jan 2004 09:03:12 +0100	[thread overview]
Message-ID: <20040110080312.GA28970@sonycom.com> (raw)
In-Reply-To: <20040110011922.GA14930@rembrandt.csv.ica.uni-stuttgart.de>

On Sat, Jan 10, 2004 at 02:19:22AM +0100, Thiemo Seufer wrote:
> [snip]
> The supposed way is to use -mabi=FOO -march=BAR, where BAR can also be
> e.g. "mips3". 

The -march=mipsN is from gcc-3.3 and higher, right ? 

> This will choose the proper (probably generic) architecture
> as well as the ISA defines. 

I expected, when using -march=r4100, that MIPS3 would be used. That was
apparently not the case (is this maybe a bug in gcc-3.2.2 ?).

> Btw, the ISA defines aren't used in the
> kernel anymore.

Well, asm-mips/asm.h still contains some #ifdef's based on the
_MIPS_ISA. 


Dimitri

-- 
Dimitri Torfs       |  NSCE 
dimitri@sonycom.com |  The Corporate Village
tel: +32 2 7008541  |  Da Vincilaan 7 - D1 
fax: +32 2 7008622  |  B-1935 Zaventem - Belgium

  reply	other threads:[~2004-01-10  8:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 11:46 Support for newer gcc/gas options Dimitri Torfs
2003-12-23 12:05 ` Maciej W. Rozycki
2004-01-09 22:01   ` Dimitri Torfs
2004-01-10  1:19     ` Thiemo Seufer
2004-01-10  8:03       ` Dimitri Torfs [this message]
2004-01-20 12:37   ` Maciej W. Rozycki
2004-01-20 12:45     ` Thiemo Seufer
2004-01-20 12:59       ` Maciej W. Rozycki
2004-01-20 20:40     ` Dimitri Torfs
2004-01-21 14:09       ` Maciej W. Rozycki
2004-01-21 14:51         ` Dimitri Torfs
2004-01-21 18:35           ` Dimitri Torfs
2004-01-22 16:10             ` Maciej W. Rozycki
2004-01-25 19:17               ` Dimitri Torfs
2004-01-26 18:08                 ` 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=20040110080312.GA28970@sonycom.com \
    --to=dimitri@sonycom.com \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    /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