> pxor instruction with xorps instead makes it work. So, that's a bug in
> gcc I suspect, using sse2 instructions when only called to use sse
> instructions. It seems odd to me that the CPU wouldn't generate an
> illegal instruction exception, but oh well, it evidently doesn't.
Remember ye goode olde 6502/6510 processors used in the famous Commodore
64 computers? These don't bail out when using undefined opcodes either,
some opcodes actually had undocumented but consistent behaviour and were
used in "my program is shorter than yours" 1000 byte demo contests and
the like.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/