summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen
diff options
context:
space:
mode:
authorTim Northover <Tim.Northover@arm.com>2013-04-20 12:32:43 +0000
committerTim Northover <Tim.Northover@arm.com>2013-04-20 12:32:43 +0000
commit16aba1702434c56c78e1ea7fe55be81d88e0f443 (patch)
treee8e0ecaa6b11f606708b32ef417eb6c707d33284 /llvm/lib/CodeGen
parenta2b533906aa83615c5f50582bb8835bd27905388 (diff)
downloadbcm5719-llvm-16aba1702434c56c78e1ea7fe55be81d88e0f443.tar.gz
bcm5719-llvm-16aba1702434c56c78e1ea7fe55be81d88e0f443.zip
Remove unused ShouldFoldAtomicFences flag.
I think it's almost impossible to fold atomic fences profitably under LLVM/C++11 semantics. As a result, this is now unused and just cluttering up the target interface. llvm-svn: 179940
Diffstat (limited to 'llvm/lib/CodeGen')
-rw-r--r--llvm/lib/CodeGen/TargetLoweringBase.cpp1
1 files changed, 0 insertions, 1 deletions
diff --git a/llvm/lib/CodeGen/TargetLoweringBase.cpp b/llvm/lib/CodeGen/TargetLoweringBase.cpp
index 82bb37ef978..8074d167f44 100644
--- a/llvm/lib/CodeGen/TargetLoweringBase.cpp
+++ b/llvm/lib/CodeGen/TargetLoweringBase.cpp
@@ -647,7 +647,6 @@ TargetLoweringBase::TargetLoweringBase(const TargetMachine &tm,
PrefFunctionAlignment = 0;
PrefLoopAlignment = 0;
MinStackArgumentAlignment = 1;
- ShouldFoldAtomicFences = false;
InsertFencesForAtomic = false;
SupportJumpTables = true;
MinimumJumpTableEntries = 4;
OpenPOWER on IntegriCloud