maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/CodeGen/x86_32-arguments-linux.c

52 lines
2.2 KiB
C
Raw Normal View History

Change -mno-mmx to be more compatible with gcc. Specifically, -mno-mmx should not imply -mno-sse. Note that because we don't usually touch the MMX registers anyway, all -mno-mmx needs to do is tweak the x86-32 calling convention a little for vectors that look like MMX vectors, and prevent the definition of __MMX__. clang doesn't actually stop the user from using MMX inline asm operands or MMX builtins in -mno-mmx mode; as a QOI issue, it would be nice to diagnose, but I doubt it really matters much. <rdar://problem/9694837> llvm-svn: 134770
2011-07-09 07:31:17 +08:00
// RUN: %clang_cc1 -w -fblocks -triple i386-pc-linux-gnu -target-cpu pentium4 -emit-llvm -o %t %s
IRgen/x86_32/Linux: Linux seems to align all stack objects to 4 bytes, unlike Darwin. Checked vs the handiest Linux llvm-gcc I had around, someone on Linux is welcome to investigate more. llvm-svn: 114112
2010-09-17 04:41:56 +08:00
// RUN: FileCheck < %t %s
// CHECK: define void @f56(
Update the tests. This update coincides with r174110. That change ordered the attributes alphabetically. llvm-svn: 174111
2013-02-01 07:17:12 +08:00
// CHECK: i8 signext %a0, %struct.s56_0* align 4 byval %a1,
// CHECK: x86_mmx %a2.coerce, %struct.s56_1* align 4 byval,
// CHECK: <1 x double> %a4, %struct.s56_2* align 4 byval,
// CHECK: <4 x i32> %a6, %struct.s56_3* align 4 byval,
// CHECK: <2 x double> %a8, %struct.s56_4* align 4 byval,
// CHECK: <8 x i32> %a10, %struct.s56_5* align 4 byval,
// CHECK: <4 x double> %a12, %struct.s56_6* align 4 byval)
IRgen/x86_32/Linux: Linux seems to align all stack objects to 4 bytes, unlike Darwin. Checked vs the handiest Linux llvm-gcc I had around, someone on Linux is welcome to investigate more. llvm-svn: 114112
2010-09-17 04:41:56 +08:00
// CHECK: call void (i32, ...)* @f56_0(i32 1,
Update the tests. This update coincides with r174110. That change ordered the attributes alphabetically. llvm-svn: 174111
2013-02-01 07:17:12 +08:00
// CHECK: i32 %{{.*}}, %struct.s56_0* align 4 byval %{{[^ ]*}},
// CHECK: x86_mmx %{{[^ ]*}}, %struct.s56_1* align 4 byval %{{[^ ]*}},
// CHECK: <1 x double> %{{[^ ]*}}, %struct.s56_2* align 4 byval %{{[^ ]*}},
// CHECK: <4 x i32> %{{[^ ]*}}, %struct.s56_3* align 4 byval %{{[^ ]*}},
// CHECK: <2 x double> %{{[^ ]*}}, %struct.s56_4* align 4 byval %{{[^ ]*}},
// CHECK: <8 x i32> %{{[^ ]*}}, %struct.s56_5* align 4 byval %{{[^ ]*}},
// CHECK: <4 x double> %{{[^ ]*}}, %struct.s56_6* align 4 byval %{{[^ ]*}})
IRgen/x86_32/Linux: Linux seems to align all stack objects to 4 bytes, unlike Darwin. Checked vs the handiest Linux llvm-gcc I had around, someone on Linux is welcome to investigate more. llvm-svn: 114112
2010-09-17 04:41:56 +08:00
// CHECK: }
//
// <rdar://problem/7964854> [i386] clang misaligns long double in structures
// when passed byval
// <rdar://problem/8431367> clang misaligns parameters on stack
typedef int __attribute__((vector_size (8))) t56_v2i;
typedef double __attribute__((vector_size (8))) t56_v1d;
typedef int __attribute__((vector_size (16))) t56_v4i;
typedef double __attribute__((vector_size (16))) t56_v2d;
typedef int __attribute__((vector_size (32))) t56_v8i;
typedef double __attribute__((vector_size (32))) t56_v4d;
struct s56_0 { char a; };
struct s56_1 { t56_v2i a; };
struct s56_2 { t56_v1d a; };
struct s56_3 { t56_v4i a; };
struct s56_4 { t56_v2d a; };
struct s56_5 { t56_v8i a; };
struct s56_6 { t56_v4d a; };
void f56(char a0, struct s56_0 a1,
t56_v2i a2, struct s56_1 a3,
t56_v1d a4, struct s56_2 a5,
t56_v4i a6, struct s56_3 a7,
t56_v2d a8, struct s56_4 a9,
t56_v8i a10, struct s56_5 a11,
t56_v4d a12, struct s56_6 a13) {
extern void f56_0(int x, ...);
f56_0(1, a0, a1, a2, a3, a4, a5, a6, a7, a8, a9,
a10, a11, a12, a13);
}