| To: | Atsushi Nemoto <nemoto@toshiba-tops.co.jp> |
|---|---|
| Subject: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA) |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Tue, 19 Aug 2003 05:52:43 +0200 |
| Cc: | kumba@gentoo.org, linux-mips@linux-mips.org |
| In-reply-to: | <20030812.182529.18309031.nemoto@toshiba-tops.co.jp> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20030812.152654.74756131.nemoto@toshiba-tops.co.jp> <3F388E0C.50802@gentoo.org> <20030812.182529.18309031.nemoto@toshiba-tops.co.jp> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Tue, Aug 12, 2003 at 06:25:29PM +0900, Atsushi Nemoto wrote: > Only affected code I found is __BUILD_clear_ade. So the 32-bit kernel > compiled with -mips3 will work fine normally, but once an address > error occur the kernel will crash. > > As Thiemo said, it seems include/asm-mips/asm.h should be fixed > instead of Makefile. Still investigating... No. We may argue if the compiler is defining the wrong symbols for given options or the Makefile passes the wrong options but the __mips64 symbol is a define that exists since 64-bit MIPS compilers exist. It simply should not be defined at this point. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Ralf Baechle |
|---|---|
| Next by Date: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Ralf Baechle |
| Previous by Thread: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Atsushi Nemoto |
| Next by Thread: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Thiemo Seufer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |