On Thu, 2010-03-18 at 08:39 -0400, Brett Smith wrote: [...] > > Are you seeing similar errors to those pasted at the bottom? This is a > > build I attempted on metad and lenny. > > > > ../../src/smi_video.c:1877: warning: unused variable 'pScreen' > > /tmp/ccBlnV2F.s: Assembler messages: > > /tmp/ccBlnV2F.s:4616: Error: illegal operands `xor $f0,$f0,$f0' > > /tmp/ccBlnV2F.s:4617: Error: opcode not supported on this processor: mips1 > > (mips1) `ldc1 $f4,($4)' > > /tmp/ccBlnV2F.s:4618: Error: unrecognized opcode `punpcklbh $f2,$f4,$f0' > > /tmp/ccBlnV2F.s:4619: Error: unrecognized opcode `punpckhbh $f4,$f4,$f0' > > /tmp/ccBlnV2F.s:4620: Error: opcode not supported on this processor: mips1 > > (mips1) `ldc1 $f16,8($4)' > > [snip] > > Yep, those are the ones. I even tried this with binutils 2.20 with the > loongson2f patch and still got this problem. > > Those opcodes are coming from some assembly code that's included > directly in the patch. This patch was written specifically for the > Loongson, so I wonder what's going on...
Should we explicitly use "set .mips3" here to tell the compiler to understand the instructins or use -march=loongson2f? I'm not sure about this problem, perhaps Xiang Yu (from Lemote) can give a help, just put him into the CC: list. Regards, _______________________________________________ gNewSense-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
