Subj : Re: Memory visibility and the C compiler... ( a bit long )
To   : comp.programming.threads
From : SenderX
Date : Sun Jan 16 2005 05:35 pm

> It can be reordered all the ways the compiler can imagine and
> the compiler cannot imagine very much about external routines.

This is the main reason I skipped using the inline assembler. I was too 
paranoid. My library is intended to be used in production server code. I 
figured that if all of my lock-free stuff was totally contained in an 
externally assembled library, most of the issues wrt compiler reordering 
would go away. I am currently revising my paper to reflect on everything 
that was discussed in this thread...

:O




p.s.

I think I was crazy to include a section on memory visibility in my paper. 
Every other paper just assumes TSO and that every single instruction will be 
executed as shown.

Yikes!

.