llvm-capstone/clang/test/Driver/fpack-struct.c

// RUN: %clang -fpack-struct -### %s 2> %t
// RUN: FileCheck < %t %s
// RUN: %clang -fpack-struct=8 -### %s 2> %t
// RUN: FileCheck < %t %s --check-prefix=CHECK-EQ

// CHECK: "-cc1"
// CHECK: "-fpack-struct=1"

// CHECK-EQ: "-cc1"
// CHECK-EQ: "-fpack-struct=8"
Fix forwarding of -fpack-struct from driver to CC1, and add a test. -fpack-struct's handling has changed in CC1 (one of only two flags that needed changing) because the driver treats "-fpack-struct" as a boolean flag, and CC1 (did) treat it as an option with a separated value. This change causes -fpack-struct=X to be forwarded correctly to -fpack-struct=X instead of erroneously to "-fpack-struct X" llvm-svn: 155981 2012-05-02 07:56:14 +00:00			`// RUN: %clang -fpack-struct -### %s 2> %t`
			`// RUN: FileCheck < %t %s`
			`// RUN: %clang -fpack-struct=8 -### %s 2> %t`
Fix FileCheck --check-prefix lines. Various tests had sprung up over the years which had --check-prefix=ABC on the RUN line, but "CHECK-ABC:" later on. This happened to work before, but was strictly incorrect. FileCheck is getting stricter soon though. Patch by Ron Ofir. llvm-svn: 188174 2013-08-12 12:51:05 +00:00			`// RUN: FileCheck < %t %s --check-prefix=CHECK-EQ`
Fix forwarding of -fpack-struct from driver to CC1, and add a test. -fpack-struct's handling has changed in CC1 (one of only two flags that needed changing) because the driver treats "-fpack-struct" as a boolean flag, and CC1 (did) treat it as an option with a separated value. This change causes -fpack-struct=X to be forwarded correctly to -fpack-struct=X instead of erroneously to "-fpack-struct X" llvm-svn: 155981 2012-05-02 07:56:14 +00:00
			`// CHECK: "-cc1"`
			`// CHECK: "-fpack-struct=1"`

			`// CHECK-EQ: "-cc1"`
			`// CHECK-EQ: "-fpack-struct=8"`