Github user ben-craig commented on the issue: https://github.com/apache/thrift/pull/981 Unless you have extremely compelling profiling results, the only atomic memory order you should be using is memory_order_seq_cst. Even better, you get seq_cst for free as the default parameter of load and store. memory_order_consume is almost entirely broken in C++11 and 14. Basically all compilers promote it to an acquire instead of a consume. memory_order_relaxed is extremely difficult to reason about, and should be avoided.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---