llvm-6502/test/MC/COFF/feat00.s

// RUN: llvm-mc -filetype=obj -triple i686-pc-win32 %s -o - | llvm-readobj -t | FileCheck %s

"@feat.00" = 123
.globl @feat.00

// CHECK: Symbol {
// CHECK:   Name: @feat.00
// CHECK:   Value: 123
// CHECK:   Section: IMAGE_SYM_ABSOLUTE (-1)
// CHECK:   BaseType: Null (0x0)
// CHECK:   ComplexType: Null (0x0)
// CHECK:   StorageClass: External (0x2)
// CHECK:   AuxSymbolCount: 0
// CHECK: }
COFF: Ensure that objects produced by LLVM link with /safeseh Summary: We indicate that the object files are safe by emitting a @feat.00 absolute address symbol. The address is presumably interpreted as a bitfield of features that the compiler would like to enable. Bit 0 is documented in the PE COFF spec to opt in to "registered SEH", which is what /safeseh enables. LLVM's object files are safe by default because LLVM doesn't know how to produce SEH handlers. Reviewers: Bigcheese CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D1691 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@190898 91177308-0d34-0410-b5e6-96231b3b80d8 2013-09-17 23:18:05 +00:00			`// RUN: llvm-mc -filetype=obj -triple i686-pc-win32 %s -o - \| llvm-readobj -t \| FileCheck %s`

			`"@feat.00" = 123`
Revert "COFF: Emit all MCSymbols rather than filtering out some of them" This reverts commit r190888, to fix PR17967. The original change wasn't the right way to get @feat.00 into the object file. The right fix is to make @feat.00 be a global symbol. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@195053 91177308-0d34-0410-b5e6-96231b3b80d8 2013-11-18 23:08:12 +00:00			`.globl @feat.00`
COFF: Ensure that objects produced by LLVM link with /safeseh Summary: We indicate that the object files are safe by emitting a @feat.00 absolute address symbol. The address is presumably interpreted as a bitfield of features that the compiler would like to enable. Bit 0 is documented in the PE COFF spec to opt in to "registered SEH", which is what /safeseh enables. LLVM's object files are safe by default because LLVM doesn't know how to produce SEH handlers. Reviewers: Bigcheese CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D1691 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@190898 91177308-0d34-0410-b5e6-96231b3b80d8 2013-09-17 23:18:05 +00:00
			`// CHECK: Symbol {`
			`// CHECK: Name: @feat.00`
			`// CHECK: Value: 123`
llvm-readobj: pretty-print special COFF section names Print IMAGE_SYM_DEBUG and the like instead of (-2). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@218172 91177308-0d34-0410-b5e6-96231b3b80d8 2014-09-20 00:25:06 +00:00			`// CHECK: Section: IMAGE_SYM_ABSOLUTE (-1)`
COFF: Ensure that objects produced by LLVM link with /safeseh Summary: We indicate that the object files are safe by emitting a @feat.00 absolute address symbol. The address is presumably interpreted as a bitfield of features that the compiler would like to enable. Bit 0 is documented in the PE COFF spec to opt in to "registered SEH", which is what /safeseh enables. LLVM's object files are safe by default because LLVM doesn't know how to produce SEH handlers. Reviewers: Bigcheese CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D1691 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@190898 91177308-0d34-0410-b5e6-96231b3b80d8 2013-09-17 23:18:05 +00:00			`// CHECK: BaseType: Null (0x0)`
			`// CHECK: ComplexType: Null (0x0)`
			`// CHECK: StorageClass: External (0x2)`
			`// CHECK: AuxSymbolCount: 0`
			`// CHECK: }`