Databases
StackOverflow2013
Postsdbo
POWhy volatile and MemoryBarrier do not prevent operations reordering?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy volatile and MemoryBarrier do not prevent operations reordering?
    primarykey
    data
    text
    <p>If I understand meaning of volatile and MemoryBarrier correctly than the program below has never to be able to show any result.</p> <p>It catches reordering of write operations every time I run it. It does not matter if I run it in Debug or Release. It also does not matter if I run it as 32bit or 64bit application.</p> <p>Why does it happen?</p> <pre><code> using System; using System.Threading; using System.Threading.Tasks; namespace FlipFlop { class Program { //Declaring these variables as volatile should instruct compiler to //flush all caches from registers into the memory. static volatile int a; static volatile int b; //Track a number of iteration that it took to detect operation reordering. static long iterations = 0; static object locker = new object(); //Indicates that operation reordering is not found yet. static volatile bool continueTrying = true; //Indicates that Check method should continue. static volatile bool continueChecking = true; static void Main(string[] args) { //Restarting test until able to catch reordering. while (continueTrying) { iterations++; var checker = new Task(Check); var writter = new Task(Write); lock (locker) { continueChecking = true; checker.Start(); } writter.Start(); checker.Wait(); writter.Wait(); } Console.ReadKey(); } static void Write() { //Writing is locked until Main will start Check() method. lock (locker) { //Using memory barrier should prevent opration reordering. a = 1; Thread.MemoryBarrier(); b = 10; Thread.MemoryBarrier(); b = 20; Thread.MemoryBarrier(); a = 2; //Stops spinning in the Check method. continueChecking = false; } } static void Check() { //Spins until finds operation reordering or stopped by Write method. while (continueChecking) { int tempA = a; int tempB = b; if (tempB == 10 &amp;&amp; tempA == 2) { continueTrying = false; Console.WriteLine("Caught when a = {0} and b = {1}", tempA, tempB); Console.WriteLine("In " + iterations + " iterations."); break; } } } } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDennis
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy volatile and MemoryBarrier do not prevent operations reordering?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy volatile and MemoryBarrier do not prevent operations reordering?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy volatile and MemoryBarrier do not prevent operations reordering?
      1. UScrypted
      1. VTFavorite
    1. COb/c this is their very idea. Memory barriers (write) just make sure all operation up to the moment are flushed, hence the following ones are ordered part the barrier.
      singulars
      1. POWhy volatile and MemoryBarrier do not prevent operations reordering?
      1. USbestsss
    2. COthe most interesting thing in your code is that removing all the `Thread.MemoryBarrier();` lines fixes your problem =)
      singulars
      1. POWhy volatile and MemoryBarrier do not prevent operations reordering?
      1. USMikant
    3. CO@Mikant: No, that does _not_ fix the problem. It just makes it very very unlikely. Let it run for a few days and it still might happen.
      singulars
      1. POWhy volatile and MemoryBarrier do not prevent operations reordering?
      1. USHenk Holterman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload