llvm/test/CodeGen/ARM/2009-10-30.ll

; RUN: llc < %s  -mtriple=arm-linux-gnueabi  | FileCheck %s
; This test checks that the address of the varg arguments is correctly
; computed when there are 5 or more regular arguments.

define void @f(i32 %a1, i32 %a2, i32 %a3, i32 %a4, i32 %a5, ...) {
entry:
;CHECK: sub	sp, sp, #4
;CHECK: add	r{{[0-9]+}}, sp, #8
;CHECK: str	r{{[0-9]+}}, [sp], #4
;CHECK: bx	lr
	%ap = alloca i8*, align 4
	%ap1 = bitcast i8** %ap to i8*
	call void @llvm.va_start(i8* %ap1)
	ret void
}

declare void @llvm.va_start(i8*) nounwind
This fixes functions like void f (int a1, int a2, int a3, int a4, int a5,...) In ARMTargetLowering::LowerFormalArguments if the function has 4 or more regular arguments we used to set VarArgsFrameIndex using an offset of 0, which is only correct if the function has exactly 4 regular arguments. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@85590 91177308-0d34-0410-b5e6-96231b3b80d8 2009-10-30 14:33:14 +00:00			`; RUN: llc < %s -mtriple=arm-linux-gnueabi \| FileCheck %s`
			`; This test checks that the address of the varg arguments is correctly`
			`; computed when there are 5 or more regular arguments.`

			`define void @f(i32 %a1, i32 %a2, i32 %a3, i32 %a4, i32 %a5, ...) {`
			`entry:`
			`;CHECK: sub sp, sp, #4`
Run codegen dce pass for all targets at all optimization levels. Previously it's only run for x86 with fastisel. I've found it being very effective in eliminating some obvious dead code as result of formal parameter lowering especially when tail call optimization eliminated the need for some of the loads from fixed frame objects. It also shrinks a number of the tests. A couple of tests no longer make sense and are now eliminated. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@95493 91177308-0d34-0410-b5e6-96231b3b80d8 2010-02-06 09:07:11 +00:00			`;CHECK: add r{{[0-9]+}}, sp, #8`
Added sub-formats to the NeonI/NeonXI instructions to further refine the NEONFrm instructions to help disassembly. We also changed the output of the addressing modes to omit the '+' from the assembler syntax #+/-<imm> or +/-<Rm>. See, for example, A8.6.57/58/60. And modified test cases to not expect '+' in +reg or #+num. For example, ; CHECK: ldr.w r9, [r7, #28] git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@98745 91177308-0d34-0410-b5e6-96231b3b80d8 2010-03-17 17:52:21 +00:00			`;CHECK: str r{{[0-9]+}}, [sp], #4`
This fixes functions like void f (int a1, int a2, int a3, int a4, int a5,...) In ARMTargetLowering::LowerFormalArguments if the function has 4 or more regular arguments we used to set VarArgsFrameIndex using an offset of 0, which is only correct if the function has exactly 4 regular arguments. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@85590 91177308-0d34-0410-b5e6-96231b3b80d8 2009-10-30 14:33:14 +00:00			`;CHECK: bx lr`
			`%ap = alloca i8*, align 4`
			`%ap1 = bitcast i8** %ap to i8*`
			`call void @llvm.va_start(i8* %ap1)`
			`ret void`
			`}`

			`declare void @llvm.va_start(i8*) nounwind`