By tag: MemoryBarrier
Ban this user: Options
Please provide a reason for deleting this story
Parallel programming can be tricky, both compiler and CPU's optimization can lead into a twilight zone's debugging.
That part I knew… what we news to me is there is a better way to do volatile, and that is with an explicitly memory barrier before accessing the data member.. We have a an API for that: System.Threading.Thread.MemoryBarrier(). This is more efficient than using volatile because a volatile field r...