f07b5ec0dc
- We do this when it is easy to determine that the backend will pass them on
the stack properly by itself.
Currently LLVM codegen is really bad in some cases with byval, for example, on
the test case here (which is derived from Sema code, which likes to pass
SourceLocations around)::
struct s47 { unsigned a; };
void f47(int,int,int,int,int,int,struct s47);
void test47(int a, struct s47 b) { f47(a, a, a, a, a, a, b); }
we used to emit code like this::
...
movl %esi, -8(%rbp)
movl -8(%rbp), %ecx
movl %ecx, (%rsp)
...
to handle moving the struct onto the stack, which is just appalling.
Now we generate::
movl %esi, (%rsp)
which seems better, no?
llvm-svn: 152462
13 lines
532 B
C
13 lines
532 B
C
// RUN: %clang_cc1 -emit-llvm %s -o %t -triple=x86_64-apple-darwin10
|
|
// RUN: FileCheck < %t %s
|
|
|
|
// Make sure this doesn't crash. We used to generate a byval here and wanted to
|
|
// verify a valid alignment, but we now realize we can use an i16 and let the
|
|
// backend guarantee the alignment.
|
|
|
|
void a(int,int,int,int,int,int,__complex__ char);
|
|
void b(__complex__ char *y) { a(0,0,0,0,0,0,*y); }
|
|
// CHECK: define void @b
|
|
// CHECK: alloca { i8, i8 }*, align 8
|
|
// CHECK: call void @a(i32 0, i32 0, i32 0, i32 0, i32 0, i32 0, i16 {{.*}})
|