@rygorous @cmuratori (LOCK prefix is broken and causes 'corruption of CPU state')
-
-
Replying to @erincandescent
@oshepherd@rygorous Ouch :( That was a 2013 part??1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@rygorous 2014. Errata disclosed February1 reply 0 retweets 0 likes -
Replying to @erincandescent
@oshepherd@cmuratori They also do not support multiple Cores at all so this is completely besides the point here. :)1 reply 0 retweets 0 likes -
Replying to @rygorous
@rygorous@oshepherd Not really, you might run code on it that was compiled to be multi-core capable, right :/1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@oshepherd Because there's so much Pentium 1-level code lying around that's trying to use multi-core? :)1 reply 0 retweets 0 likes -
Replying to @rygorous
@cmuratori@oshepherd Quark is 32-bit only, no MMX, no SSE, no CMOVs...1 reply 0 retweets 0 likes -
Replying to @rygorous
@cmuratori@oshepherd you can't use your existing compiled code for that no matter what; all mainstream x86 compilers started requiring...1 reply 0 retweets 0 likes -
Replying to @rygorous
@cmuratori@oshepherd PPro-level instructions by default sometime during the last decade. :)3 replies 0 retweets 1 like -
Replying to @rygorous
@rygorous@oshepherd Ah, OK - that's probably safe then, yes :) Although the lock prefix dates back to at least the 386...1 reply 0 retweets 0 likes
@rygorous @oshepherd ... not totally sure who was actually using it, though...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.