On Dec 27, 2011, at 9:53 PM, Greg Ungerer wrote:
if (CPU_IS_COLDFIRE) {
__asm__ volatile ("fsave %0"
: : "m" (*sc->sc_fpstate) :
"memory");
} else {
__asm__ volatile (".chip 68k/68881\n\t"
"fsave %0\n\t"
".chip 68k"
: : "m" (*sc->sc_fpstate) :
"memory");
}
I am still concerned about the use of ".chip 68k" in general though.
Just not sure how we can avoid it. I guess there is no way to jus
t revert to the original CPU choice?
#define CPU "68040"
_asm__ volatile (".chip 68k/68881\n\t"
"fsave %0\n\t"
".chip " CPU
: : "m" (*sc->sc_fpstate) : "memory");
Josh
--
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
