| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Re: -mcpu vs. binutils 2.13.90.0.18 |
| From: | Guido Guenther <agx@sigxcpu.org> |
| Date: | Tue, 18 Mar 2003 18:42:41 +0100 |
| In-reply-to: | <20030318160303.GN13122@rembrandt.csv.ica.uni-stuttgart.de> |
| Mail-followup-to: | Guido Guenther <agx@sigxcpu.org>, linux-mips@linux-mips.org |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20030318154155.GF2613@bogon.ms20.nix> <20030318160303.GN13122@rembrandt.csv.ica.uni-stuttgart.de> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4i |
On Tue, Mar 18, 2003 at 05:03:03PM +0100, Thiemo Seufer wrote: > Try > -mabi=o32 -march=r5000 -Wa,--trap > This may fail if the compiler is very old, though. > > > for IP22? -mips2 conflicts with -march=r5000 since this implies -mips4. > > This was fixed in very recent gcc. -mips2 should be an alias for -march=r6000 > and -mips4 one for -march=r8000. Is it correct that -mipsX in contrast to -march=rXXXX has the difference of not only selecting a specific CPU instruction set but also an abi (o32 or n64)? If so wouldn't it be cleaner to remove -mipsX altogether and use -march=rXXXX and -mabi=o32, etc? The different meanings of these options in different toolchain versions confuse me a lot. What is the final intended usage of these options? -- Guido |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | 2.4.20 SCSI problems on NASRaQ, Neurophyre |
|---|---|
| Next by Date: | Re: -mcpu vs. binutils 2.13.90.0.18, Thiemo Seufer |
| Previous by Thread: | Re: -mcpu vs. binutils 2.13.90.0.18, Thiemo Seufer |
| Next by Thread: | Re: -mcpu vs. binutils 2.13.90.0.18, Thiemo Seufer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |