From: Chris Lattner <sabre@nondot.org>
Date: Tue, 21 Jul 2009 22:37:38 +0000 (+0000)
Subject: if Xcore doesn't support TLS, it doesn't have to worry about thread local LLVM IR... 
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=684d5fe95dc696916e58085aa95afe19402d1165;p=platform%2Fupstream%2Fllvm.git

if Xcore doesn't support TLS, it doesn't have to worry about thread local LLVM IR, it should be rejected by a front-end.

llvm-svn: 76665
---

diff --git a/llvm/lib/Target/XCore/XCoreTargetAsmInfo.cpp b/llvm/lib/Target/XCore/XCoreTargetAsmInfo.cpp
index cf27a51..8a9f0c2 100644
--- a/llvm/lib/Target/XCore/XCoreTargetAsmInfo.cpp
+++ b/llvm/lib/Target/XCore/XCoreTargetAsmInfo.cpp
@@ -72,7 +72,7 @@ unsigned XCoreTargetAsmInfo::
 SectionFlagsForGlobal(const GlobalValue *GV, const char* Name) const {
   unsigned Flags = ELFTargetAsmInfo::SectionFlagsForGlobal(GV, Name);
   // Mask out unsupported flags
-  Flags &= ~(SectionFlags::Small | SectionFlags::TLS);
+  Flags &= ~SectionFlags::Small;
 
   // Set CP / DP relative flags
   if (GV) {