summaryrefslogtreecommitdiff
path: root/lib/VMCore/Globals.cpp
diff options
context:
space:
mode:
authorOwen Anderson <resistor@mac.com>2009-06-20 00:24:58 +0000
committerOwen Anderson <resistor@mac.com>2009-06-20 00:24:58 +0000
commit04fb7c36a9977127f32558dc01c39a9c2388bc39 (patch)
treeca25bb398da7dc1232611d29ce1d1b301341dfe0 /lib/VMCore/Globals.cpp
parentd5fb7906130989a579d1bfe4490b414331e94fee (diff)
downloadllvm-04fb7c36a9977127f32558dc01c39a9c2388bc39.tar.gz
llvm-04fb7c36a9977127f32558dc01c39a9c2388bc39.tar.bz2
llvm-04fb7c36a9977127f32558dc01c39a9c2388bc39.tar.xz
Revert r73790, and replace it with a significantly less ugly solution. Rather than trying to make the global reader-writer lock work,
create separate recursive mutexes for each value map. The recursive-ness fixes the double-acquiring issue, which having one per ValueMap lets us continue to maintain some concurrency. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@73801 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/VMCore/Globals.cpp')
-rw-r--r--lib/VMCore/Globals.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/VMCore/Globals.cpp b/lib/VMCore/Globals.cpp
index a7799ea4f1..5abe1f9ac4 100644
--- a/lib/VMCore/Globals.cpp
+++ b/lib/VMCore/Globals.cpp
@@ -75,7 +75,7 @@ void GlobalValue::removeDeadConstantUsers() const {
/// Override destroyConstant to make sure it doesn't get called on
/// GlobalValue's because they shouldn't be treated like other constants.
-void GlobalValue::destroyConstant(bool locked) {
+void GlobalValue::destroyConstant() {
assert(0 && "You can't GV->destroyConstant()!");
abort();
}