From: Chris Lattner 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://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=27391795acc2dcf4f7935343ad3dea35c619e76b;p=oota-llvm.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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@76665 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/lib/Target/XCore/XCoreTargetAsmInfo.cpp b/lib/Target/XCore/XCoreTargetAsmInfo.cpp index cf27a51d281..8a9f0c2748b 100644 --- a/lib/Target/XCore/XCoreTargetAsmInfo.cpp +++ b/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) {