From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>
Cc: kumba@gentoo.org, linux-mips@linux-mips.org
Subject: Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA)
Date: Tue, 19 Aug 2003 05:52:43 +0200 [thread overview]
Message-ID: <20030819035242.GB6223@linux-mips.org> (raw)
In-Reply-To: <20030812.182529.18309031.nemoto@toshiba-tops.co.jp>
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
next prev parent reply other threads:[~2003-08-19 3:52 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 [this message]
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
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=20030819035242.GB6223@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=nemoto@toshiba-tops.co.jp \
/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