News for hackers. Stuff that matters.
Re:Why volatile is hard to specify and implement by rdtsc on Monday April 11, 2016 @01:13AM (#11469758)
It was memory used for a low latency system, didn't have locks even spinlocks. In that case it was manipulating data directly in shm and compiler was optimizating away access to data. What is the current/modern mechanism to ensure a stucture or flag won't be optimized away from shared memory mapped between two processes? Are access functions available in userspace libraries?

There are no comments on this comment yet.