diff options
| author | John McCall <rjmccall@apple.com> | 2011-09-21 08:08:30 +0000 |
|---|---|---|
| committer | John McCall <rjmccall@apple.com> | 2011-09-21 08:08:30 +0000 |
| commit | 01f151e0ffba72bcad770bea5f563a9b68ca050e (patch) | |
| tree | 82059ede608914861b730d6334f0e312456da3a9 /test/CodeGen/functions.c | |
| parent | 036277e3e7bfa3ccef96fabf0b34a75d9a7c015b (diff) | |
ANSI C requires that a call to an unprototyped function type succeed
if the definition has a non-variadic prototype with compatible
parameters. Therefore, the default rule for such calls must be to
use a non-variadic convention. Achieve this by casting the callee to
the function type with which it is required to be compatible, unless
the target specifically opts out and insists that unprototyped calls
should use the variadic rules. The only case of that I'm aware of is
the x86-64 convention, which passes arguments the same way in both
cases but also sets a small amount of extra information; here we seek
to maintain compatibility with GCC, which does set this when calling
an unprototyped function.
Addresses PR10810 and PR10713.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@140241 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/CodeGen/functions.c')
| -rw-r--r-- | test/CodeGen/functions.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/test/CodeGen/functions.c b/test/CodeGen/functions.c index e51f93e574..28e4bd0c82 100644 --- a/test/CodeGen/functions.c +++ b/test/CodeGen/functions.c @@ -1,4 +1,4 @@ -// RUN: %clang_cc1 %s -emit-llvm -o - -verify | FileCheck %s +// RUN: %clang_cc1 %s -triple i386-unknown-unknown -emit-llvm -o - -verify | FileCheck %s int g(); @@ -24,7 +24,7 @@ void f0() {} void f1(); void f2(void) { -// CHECK: call void @f1() +// CHECK: call void bitcast (void ()* @f1 to void (i32, i32, i32)*)(i32 1, i32 2, i32 3) f1(1, 2, 3); } // CHECK: define void @f1() |