llvm-project/clang/test/CodeGen/2008-07-22-bitfield-init-af...

// RUN: %clang_cc1 -triple=i686-apple-darwin9 -emit-llvm -o - %s | FileCheck %s

struct et7 {
  float lv7[0];
  char mv7:6;
} yv7 = {
  {}, 
  52, 
};

// CHECK: @yv7 = global %struct.et7 { [0 x float] zeroinitializer, i8 52 }
Update tests to use %clang_cc1 instead of 'clang-cc' or 'clang -cc1'. - This is designed to make it obvious that %clang_cc1 is a "test variable" which is substituted. It is '%clang_cc1' instead of '%clang -cc1' because it can be useful to redefine what gets run as 'clang -cc1' (for example, to set a default target). llvm-svn: 91446 2009-12-16 04:14:24 +08:00			`// RUN: %clang_cc1 -triple=i686-apple-darwin9 -emit-llvm -o - %s \| FileCheck %s`
Fix crash during initialization of a bitfield which followed a zero length element. Fix some 80-col violations. llvm-svn: 54610 2008-08-10 15:00:24 +08:00
			`struct et7 {`
			`float lv7[0];`
			`char mv7:6;`
			`} yv7 = {`
			`{},`
			`52,`
			`};`

CodeGen: ConstStructBuilder must verify packed constraints after padding This reverts commit r220169 which reverted r220153. However, it also contains additional changes: - We may need to add padding after we've packed the struct. This occurs when the aligned next field offset is greater than the new field's offset. When this occurs, we make the struct packed. However, once packed the next field offset might be less than the new feild's offset. It is in this case that we might further pad the struct. - We would pad structs which were perfectly sized! This behavior is immensely old. This behavior came from blindly subtracting NextFieldOffsetInChars from RecordSize. This doesn't take into account the fact that the struct might have a greater overall alignment than the last field. llvm-svn: 220175 2014-10-20 07:40:06 +08:00			`// CHECK: @yv7 = global %struct.et7 { [0 x float] zeroinitializer, i8 52 }`