Ah yes, kudos to AmiDog for the diffs.
I wonder how feasible it would be to patch these functions?
The thing is, these are CPU instructions, and they do not generate exception (or generate it too late), thus there is no way to catch them with the emulation library.
The only way to handle these transparently (without need to patch the binaries) is to run some sort of full emulation all the time, and this is slow, and surely beats the whole purpose of the ColdFire CPU.
And what kind of performance could we expect?
For full compatibility (those missing user instructions, the user instructions behaving differently and supervisor emulation), I'd still estimate slower than 68060 @ 50.
If compatibility would be lowered, and the code would mostly construct out of supported instructions, then it would certainly be faster. But again, IMO this beats the purpose.