|
From: M. R. B. <mr...@0x...> - 2001-08-08 02:07:48
|
* Greg Banks <gb...@po...> on Wed, Aug 08, 2001: > > Huh? I seem to remember we had a problem where the gcc maintainers > were making this (incorrect) assumption. So, using -m4-nofpu resulted > in __sh3__ being defined instead of __sh4__. But I thought that had > been cleared up by now. > There was a thread on this awhile back. m4-nofpu is an alias for the sh3, as the sh3 code in gcc can't generate fpu code. So the name 'm4-nofpu' itself is a misnomer. As always, blame the gcc people ;-). M. R. |