* Satish Vasudeva: > Looking back at the description in > https://gcc.gnu.org/legacy-ml/gcc-patches/2017-01/msg02344.html It > sounds like CAS based implementation is a problem for volatile atomic > loads. Can any one please elaborate what is the issue with volatile > atomic loads. I am trying to do risk analysis in our code. The page could be mapped read-only (say if it's in memory shared across processes). Reading such values using CAS will fault, so CAS is not a full replacement. Thanks, Florian
