diff options
| author | kinuko <kinuko@chromium.org> | 2015-12-20 23:11:18 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-12-21 07:12:19 +0000 |
| commit | e0012b1788305f597dd5c14e79a1f796dc3bbaf2 (patch) | |
| tree | 82db8c7f155a38c9bce1d2b2287c2ca8246c0c13 /gin/converter_unittest.cc | |
| parent | cb526e637d1f69e898a833f58eec9a59745250bf (diff) | |
| download | chromium_src-e0012b1788305f597dd5c14e79a1f796dc3bbaf2.zip chromium_src-e0012b1788305f597dd5c14e79a1f796dc3bbaf2.tar.gz chromium_src-e0012b1788305f597dd5c14e79a1f796dc3bbaf2.tar.bz2 | |
Rename DEFINE_STATIC_LOCAL_THREAD_SAFE to DEFINE_THREAD_SAFE_STATIC_LOCAL
We once renamed this from AtomicallyInitializedStaticReference
but had feedback on the rename CL [1] (that was commited already)
that 'THREAD_SAFE' is a bit unclear, which feels to make sense.
[1] https://codereview.chromium.org/1528003002/#msg14
The new name corresponds to some compilers term:
- clang/gcc disables this with the flag -fno-threadsafe-statics
- MSDN refers to this as 'thread-safe "magic" statics':
https://msdn.microsoft.com/en-us/library/hh409293.aspx
BUG=548217
Review URL: https://codereview.chromium.org/1528303003
Cr-Commit-Position: refs/heads/master@{#366344}
Diffstat (limited to 'gin/converter_unittest.cc')
0 files changed, 0 insertions, 0 deletions