> Looks like these "Illegal operands" errors from the assembler started after
> the move to gcc4, the offending asm code looks like
> fdtox %f12, %f9
> fdtox %f10, %f15
> fdtox %f8, %f9
> fdtox %f12, %f7
> Any suggestions?
I have started to investigate this. This sounds like the good `oh wait,
coercing a mutiple-register value into a single register type uses a
different register number on big-endian platforms? but it works on x86!'
recurring bug which has been biting us in subtle cases since gcc 2.95.
In the meantime I'd suggest compiling this port with -fno-tree-ter on
sparc64 (and maybe all BE64 platforms).