architecture - Are partially updated values when multithreading still a concern on modern CPUs? -

From

to:

The reason is that it is safe to remove the reader along with phase The modern CPU's terminology is guaranteed that readers will see an old or new data structure rather than a partly updated reference.

Is it all modern CPUs (ARM, X86, PPC, etc.)? Is it likely to change in the future? It feels great to never have to pay the cost of loading the lock, unless you probably have not considered the old value again (this is probably not a problem for many apps - basically For any app that can be used

OK if you are the type of primitive type and lieutenant; = This is true if the database size and data are aligned properly, so this is your Depending on the code, then on a modern CPU.

You might assume that it will be in existence because it is impossible to write garbage collectors if there are partial update pointers and lock prefix around each single signal access Use will completely kill performance.

So yes, the article is correct (again assuming size and alignment).