summaryrefslogtreecommitdiffstats
path: root/runtime/atomic.h
diff options
context:
space:
mode:
authorIan Rogers <irogers@google.com>2014-05-19 22:55:00 -0700
committerIan Rogers <irogers@google.com>2014-05-19 22:55:00 -0700
commit63c5dd056fa20993b35ec5c8548b26c988445763 (patch)
tree53a306489c89fa69a756e37fbcaebffcfac04a82 /runtime/atomic.h
parent1a5ff7c3a6508deacd3fd6473de80c62f7316a81 (diff)
downloadart-63c5dd056fa20993b35ec5c8548b26c988445763.tar.gz
art-63c5dd056fa20993b35ec5c8548b26c988445763.tar.bz2
art-63c5dd056fa20993b35ec5c8548b26c988445763.zip
Fix the sense of when mutexes are used for longs in atomic support.
Change-Id: Ice50519a511e98fdc2fe74cd9eb77c32872022b4
Diffstat (limited to 'runtime/atomic.h')
-rw-r--r--runtime/atomic.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/runtime/atomic.h b/runtime/atomic.h
index 6867fefb05..1f975dc0ce 100644
--- a/runtime/atomic.h
+++ b/runtime/atomic.h
@@ -196,7 +196,7 @@ class QuasiAtomic {
// Does the architecture provide reasonable atomic long operations or do we fall back on mutexes?
static bool LongAtomicsUseMutexes() {
- return !kNeedSwapMutexes;
+ return kNeedSwapMutexes;
}
static void MembarLoadStore() {