Hi Andreas, Geert,
On 24/05/11 18:06, Andreas Schwab wrote:
Geert Uytterhoeven<geert@xxxxxxxxxxxxxx> writes:
What exactly do you mean by "does not support anything less"? It seems it does
restrict instruction generation to 68000 if you ask for it.
The point is that Linux/m68k requires 68020+, so compiling for 68000
does not make sense (at least back when the gcc configuration was
created).
Yeah, used to be true :-)
This seems very much to me to be a "broken compiler" issue.
Is it worth putting some form of compiler version limits to protect
compilation in the m68000 case? (Probably no need to limit it for
the existing 68020+ case).
Are there any other gcc defines that we could use instead?
We need to check with your old compiler Geert :-)
I really don't want to use CONFIG_MMU here (or in bitops.h either).
When I work in the ColdFire MMU code this won't be right.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@xxxxxxxxxxxx
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
