Joern RENNECKE <[EMAIL PROTECTED]> wrote: > I can't justify spending the amount time that it would take to make the > sh64 port regression free. > The lack of a debugger that works reliably with recent gcc versions has > led to an increasing > backlog of uninvestigated execution failures.
Although I know nothing about the execution failures, I've seen some compile time errors in c/c++ test for sh64-unknown-linux-elf http://gcc.gnu.org/ml/gcc-testresults/2005-09/msg00466.html 3 tests gcc.c-torture/compile/simd-4.c gcc.c-torture/execute/20050604-1.c gcc.dg/torture/pr21817-1.c fail with the similar ICE: gcc/gcc/testsuite/gcc.c-torture/compile/simd-4.c: In function 'tempf': gcc/gcc/testsuite/gcc.c-torture/compile/simd-4.c:15: error: unable to find a register to spill in class 'GENERAL_REGS' gcc/gcc/testsuite/gcc.c-torture/compile/simd-4.c:15: error: this is the insn: (insn 53 52 54 0 (set (subreg:DI (reg:V4SF 68 fr4 [196]) 0) (and:DI (subreg:DI (reg:V4SF 68 fr4 [196]) 0) (const_int -4294967296 [0xffffffff00000000]))) 85 {anddi3} (nil) (nil)) It seems odd that the DImode subregs of V4SFmode registers are used as the operands of logical operations, though I don't understand why reload complains as above. Regards, kaz
