| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA) |
| From: | Atsushi Nemoto <anemo@mba.ocn.ne.jp> |
| Date: | Wed, 13 Aug 2003 00:26:44 +0900 (JST) |
| In-reply-to: | <20030812101625.GJ23104@rembrandt.csv.ica.uni-stuttgart.de> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20030812065118.GD23104@rembrandt.csv.ica.uni-stuttgart.de> <20030812.190636.39150536.nemoto@toshiba-tops.co.jp> <20030812101625.GJ23104@rembrandt.csv.ica.uni-stuttgart.de> |
| Sender: | linux-mips-bounce@linux-mips.org |
>>>>> On Tue, 12 Aug 2003 12:16:25 +0200, Thiemo Seufer >>>>> <ica2_ts@csv.ica.uni-stuttgart.de> said: >> Does anybody know why __BUILD_clear_ade uses MFC0 and REG_S >> though other parts using mfc0 and sw ? Thiemo> Probably because BADVADDR has to be 64bit for 64bit Thiemo> kernels. :-) If so, MFC0 and REG_S should be controlled by __mips64 (or CONFIG_MIPS64) as you and Maciej W. Rozycki said in other mails. I wonder why currently is not. Historical reason ? :-) Now I'm looking 2.6 codes and there is same problem. But 2.6 codes does not use REG_S at all so the stack corruption will never happen. FYI. --- Atsushi Nemoto |
| Previous by Date: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Maciej W. Rozycki |
|---|---|
| Next by Date: | Re: [patch] Generic time trailing clean-ups, Jun Sun |
| Previous by Thread: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Thiemo Seufer |
| Next by Thread: | Re: GCCFLAGS for gcc 3.3.x (-march and _MIPS_ISA), Thiemo Seufer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |