llvm-project/llvm/test/CodeGen/PowerPC/2008-01-25-EmptyFunction.ll

; RUN: llvm-as < %s | llc -march=ppc32 | grep nop

define void @bork() noreturn nounwind  {
entry:
        unreachable
}
Need to convert to LLVM code and not C. llvm-svn: 46397 2008-01-26 14:56:08 +08:00			`; RUN: llvm-as < %s \| llc -march=ppc32 \| grep nop`
If we have a function like this: void bork() { int address = 0; address = 0; } It's compiled into LLVM code that looks like this: define void @bork() noreturn nounwind { entry: unreachable } This is bad on some platforms (like PPC) because it will generate the label for the function but no body. The label could end up being associated with some non-code related stuff, like a section. This places a "trap" instruction if the SimplifyCFG pass removed all code from the function leaving only one "unreachable" instruction. llvm-svn: 46387 2008-01-26 09:43:44 +08:00
Need to convert to LLVM code and not C. llvm-svn: 46397 2008-01-26 14:56:08 +08:00			`define void @bork() noreturn nounwind {`
			`entry:`
			`unreachable`
If we have a function like this: void bork() { int address = 0; address = 0; } It's compiled into LLVM code that looks like this: define void @bork() noreturn nounwind { entry: unreachable } This is bad on some platforms (like PPC) because it will generate the label for the function but no body. The label could end up being associated with some non-code related stuff, like a section. This places a "trap" instruction if the SimplifyCFG pass removed all code from the function leaving only one "unreachable" instruction. llvm-svn: 46387 2008-01-26 09:43:44 +08:00			`}`