atomic_thread_fence

Acquire-Release Fences

25 July 2016

Acquire and release fences guarantees similar synchronisation and ordering constraints as atomics with acquire-release semantic. Similar, because the differences are in the details.

Comments 11Views: 8617

22 July 2016

The key idea of a std::atomic_thread_fence is, to establish synchronisation and ordering constraints between threads without an atomic operation.

Comments 8Views: 16426

Today 177

All 1091399

Currently are 180 guests and no members online

No New New: Raw Pointers Removed from C++
Adrian

Hello, I appreciate a lot the fact that the commitee is working on ways to improve cpp safety, but I ...
Read more...
C++ Core Guidelines: Type Erasure with Templates
Ivan Bobev

I think that std::move in the line `Object(const T& obj): object(std::make_shared(std::move(obj))){}` ...
Read more...
Acquire-Release Semantic - The typical Misunderstanding
Rainer Grimm

If you use relaxed ordering, you lose the acquire-release semantic and, therefore, get a data race. For ...
Read more...
C++ is Lazy: CRTP
HGH

return !(op1 == op2); That doesn't look right
Read more...
Acquire-Release Semantic - The typical Misunderstanding
Jeff

If some non-atomic shared objects don't be accessed concurrently, can it just use relaxed? For example ...
Read more...