Newest Pentium bug (fatal)
Sean Eric Fagan
sef@Kithrup.COM
Sun Nov 9 14:38:00 GMT 1997
Actually, I've known about it for a few months. I verified
it back then. It's a real bug. The bug occurs when you
do two illegal things at once:
1) use the invalid opcode cmpxchg8b EAX
2) put a lock prefix on a non-read/modify/write instruction.
Both conditions are already illegal. However instead of
generating an invalid opcode exception, the processor locks
up.
Based on a later message on the list I just saw, it looks like Intel cleared
this up in newer versions of the processor.
---------------------------
(Alex typing now): As far as I personally have seen, this isn't the case,
and just about every P5 (not P5 OverDrive, or P6, or K6, or 6x86) is
vunerable. Way to go Intel.
- alex
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
More information about the Cygwin
mailing list