Why does C#’s Thread.MemoryBarrier() use “lock or” instead of mfence?
I was reading some older MS documentation, The C# Memory Model in Theory and Practice, Part 2 and was interested to read:
I was reading some older MS documentation, The C# Memory Model in Theory and Practice, Part 2 and was interested to read: