[concurrency-interest] AtomicReferenceweakCompareAndSet "Mayfailspuriously"?

[Shaffer, Darron]

So, as you turn the crank some display would say something like:

   Read of this.field, possible values: 5, 25, 17.

This would be a real challenge to write.  Not just making it figure out
all the possibilities from multiple threads, but also coming up with a
clear an usable display.  And a properly written program would make *no*
use of the hardest part of the work!


-----Original Message-----
From: concurrency-interest-bounces at cs.oswego.edu
[mailto:concurrency-interest-bounces at cs.oswego.edu] On Behalf Of Pete
Soper
Sent: Sunday, May 28, 2006 9:47 PM
To: Bill Pugh
Cc: concurrency-interest at cs.oswego.edu; dholmes at ieee.org
Subject: Re: [concurrency-interest] AtomicReferenceweakCompareAndSet
"Mayfailspuriously"?

<snip>

I'm ready for the visible VM. Just turn the crank very, very slowly and 
all will be revealed. So in this case the surprising/not 
apparent/spurious/data race order is "read null, write int[], read 
int[], write int[]{1}".

-Pete