[PATCH] D31516: Separate {Min, Max}AtomicLockFreeWidth from MaxAtomicInlineWidth

[Dan Gohman via Phabricator via llvm-commits]

sunfish added a comment.

There could conceivably be CPUs where 32-bit CAS is not the most efficient way to implement an 8-bit or 16-bit atomic operation. The other assumption is that 8-bit and 16-bit are much less important here, so the benefit of making the guarantee isn't seen to be worth the risks at this time. With backwards compatibility, one can always add guarantees that turn out to be useful in the future, but not remove guarantees that turn out to be harmful.

For further questions, I encourage you to file an issue at the threads proposal repository <https://github.com/WebAssembly/threads>. The proposed lock-free guarantee is currently stated here <https://github.com/WebAssembly/threads/blob/master/proposals/threads/Overview.md#lock-free-guarantees>.


Repository:
  rL LLVM

https://reviews.llvm.org/D31516