llvm-project/llvm/test/CodeGen/X86/coff-feat00.ll

; RUN: llc -O0 -mtriple=i386-pc-win32 -filetype=asm -o - %s | FileCheck %s

define i32 @foo() {
  ret i32 0
}

; CHECK: .set @feat.00, 1
Revert "Re-commit r192758 - MC: quote tricky symbol names in asm output" This caused the clang-native-mingw32-win7 buildbot to break. The assembler was complaining about the following lines that were showing up in the asm for CrashRecoveryContext.cpp: movl $"__ZL16ExceptionHandlerP19_EXCEPTION_POINTERS@4", 4(%eax) calll "_AddVectoredExceptionHandler@8" .def "__ZL16ExceptionHandlerP19_EXCEPTION_POINTERS@4"; "__ZL16ExceptionHandlerP19_EXCEPTION_POINTERS@4": calll "_RemoveVectoredExceptionHandler@4" Reverting for now. llvm-svn: 192940 2013-10-18 10:14:40 +08:00			`; RUN: llc -O0 -mtriple=i386-pc-win32 -filetype=asm -o - %s \| FileCheck %s`
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 llvm-svn: 190898 2013-09-18 07:18:05 +08:00
			`define i32 @foo() {`
			`ret i32 0`
			`}`

Use .set instead of = when printing assignment in assembly output On Hexagon "x = y" is a syntax used in most instructions, and is not treated as a directive. Differential Revision: https://reviews.llvm.org/D44256 llvm-svn: 328635 2018-03-28 00:44:41 +08:00			`; CHECK: .set @feat.00, 1`