StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Fix highlight typo

Browse Source
This commit is contained in:
Sachin Joseph 2015-09-22 16:29:39 +05:30
parent ec37d1ac0c
commit 256461b818
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CppCoreGuidelines.md
View File

@ -8051,7 +8051,7 @@ Speaking of concurrency, should there be a note about the dangers of std::atomic
A lot of people, myself included, like to experiment with std::memory_order, but it is perhaps best to keep a close watch on those things in production code. A lot of people, myself included, like to experiment with std::memory_order, but it is perhaps best to keep a close watch on those things in production code.
Even vendors mess this up: Microsoft had to fix their `shared_ptr` Even vendors mess this up: Microsoft had to fix their `shared_ptr`
(weak refcount decrement wasn't synchronized-with the destructor, if I recall correctly, although it was only a problem on ARM, not Intel) (weak refcount decrement wasn't synchronized-with the destructor, if I recall correctly, although it was only a problem on ARM, not Intel)
and everyone (gcc, clang, Microsoft, and intel) had to fix their c`ompare_exchange_*` this year, and everyone (gcc, clang, Microsoft, and intel) had to fix their `compare_exchange_*` this year,
after an implementation bug caused losses to some finance company and they were kind enough to let the community know. after an implementation bug caused losses to some finance company and they were kind enough to let the community know.
It should definitely mention that `volatile` does not provide atomicity, does not synchronize between threads, and does not prevent instruction reordering (neither compiler nor hardware), and simply has nothing to do with concurrency. It should definitely mention that `volatile` does not provide atomicity, does not synchronize between threads, and does not prevent instruction reordering (neither compiler nor hardware), and simply has nothing to do with concurrency.