Greg Ungerer <[email protected]> writes: > But even still, compiling with -m68040 causes gcc to generate > different code than compiling without it (so effectively with m68020). > In cases I looked at the instructions used where still fine to run > on either, so nothing specific to the 68040 was generated. But if > anything ever was then again the ".chip 68k" would cause an error > out. I guess there isn't much extra in the 68040... move16, anything > else? I guess gcc will never generate that in practice, so it is > not a problem.
The only 040 specific insn that gcc would generate are the fpu insns, but the kernel does not use any floating point. Andreas. -- Andreas Schwab, [email protected] GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
