What did C++ do for Transactional Memory?
summary
SG5 pushes a concrete TM proposal into C++ with language words like atomic_cancel semantics and synchronize alongside transaction safe/unsafe annotations; implementations range from pure STM (GCC/Intel STM) to HTM on Intel Haswell TSX and IBM Power. Two user studies show error rates fall from ~58–75% with locks to ~8–20% with TM, and a Quake server STM study shows better scaling past 3–4 threads. Rollback handles conflicts, printing and complex exceptions require workarounds; specification aims for a TS.
AI-written summary · about
chapters (4)
related talks
01h 33mWhy You Should Use Software Transactional Memory
01h 13mTransactional memory
01h 01mUnderstanding Hardware Transactional Memory
30mImplementing and Verifying Release-Acquire Transactional Memory in C11
01h 03m“Transactional Memory in Practice"
18mThe Semantics of Transactions and Weak Memory in x86, Power, ARM, and C++
15mHTMFS: Strong Consistency Comes for Free with Hardware Transactional Memory...
36mATOMICALLY { DELETE YOUR ACTORS }