llvm-project/llvm/test/FrontendC/2007-05-07-PaddingElements.c

// PR 1278
// RUN: %llvmgcc %s -S -emit-llvm -O0 -o - | grep {struct.s} | not grep "4 x i8] zeroinitializer"
// RUN: %llvmgcc %s -S -emit-llvm -O0 -o - | not grep "i32 0, i32 2"
struct s {
  double d1;
  int s1;
};

struct s foo(void) {
  struct s S = {1.1, 2};
  return S;
}
New test. llvm-svn: 36930 2007-05-08 14:10:12 +08:00			`// PR 1278`
See test. Judging from PR 1278, at the time the test was committed, the generated code was apparently doing stores directly into the return value aggregate; now, it's doing a copy from a compiler-generated static object. That object is initialized using [4 x i8] which breaks the test. I believe this change preserves the original point of the test. Of course it would be better for the code to do stores directly into the return aggregate, but that is not what happens at -O0; the llvm optimizers seem to do that on x86 but not on ppc32, possibly because of the explicit padding (which is unavoidable). I think it must have been being done by a gcc optimizer pass before. llvm-svn: 73972 2009-06-24 02:03:49 +08:00			`// RUN: %llvmgcc %s -S -emit-llvm -O0 -o - \| grep {struct.s} \| not grep "4 x i8] zeroinitializer"`
New test. llvm-svn: 36930 2007-05-08 14:10:12 +08:00			`// RUN: %llvmgcc %s -S -emit-llvm -O0 -o - \| not grep "i32 0, i32 2"`
			`struct s {`
			`double d1;`
			`int s1;`
			`};`

			`struct s foo(void) {`
			`struct s S = {1.1, 2};`
			`return S;`
			`}`