Multiple ChoiceIntermediate 45s
Memory Fence Ordering Semantics
What does std::atomic_thread_fence(std::memory_order_acquire) primarily establish?
Options
- 1It forces all writes globally visible immediately
- 2It is a full sequential-consistency barrier always
- 3It imposes acquire ordering on subsequent loads in the thread
- 4It has no ordering effect without an atomic load
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.