summaryrefslogtreecommitdiffstats
path: root/base
diff options
context:
space:
mode:
authormark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-08-13 18:11:04 +0000
committermark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-08-13 18:11:04 +0000
commitab295637537b23093388b1dc0b8395e7f4c2088d (patch)
tree6e772ff95be068dcc04d7baaac7d50c5c67992c6 /base
parent199ed63f28098561badf54c521282f1c43ca91a6 (diff)
downloadchromium_src-ab295637537b23093388b1dc0b8395e7f4c2088d.zip
chromium_src-ab295637537b23093388b1dc0b8395e7f4c2088d.tar.gz
chromium_src-ab295637537b23093388b1dc0b8395e7f4c2088d.tar.bz2
Use -fno-threadsafe-statics to disable thread-safe static semantics in C++.
This will eliminate the cxa_guard_acquire/release locks around static guard accesses. The Windows compiler doesn't support thread-safe statics at all, so none of our cross-platform code relies on thread safety. We are using -fno-threadsafe-statics on Linux as well, since r20616. It's likely that threading is not a concern in most to all Mac-specific code using statics. BUG=16713 TEST=none Review URL: http://codereview.chromium.org/165461 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23326 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
0 files changed, 0 insertions, 0 deletions