llvm-project/clang/test/CodeGenObjC/interface.m

// RUN: %clang_cc1 -triple i386-apple-darwin9 -fobjc-runtime=macosx-fragile-10.5 -O3 -emit-llvm -o %t %s
// RUN: grep 'ret i32 385' %t

void *alloca(unsigned);

@interface I0 {
@public
  int iv0;
  int iv1;
  int iv2;
}
@end

static int f0(I0 *a0) {
  return (*(a0 + 2)).iv0;
}

static int f1(I0 *a0) {
  return a0[2].iv1;
}

static int f2(I0 *a0) {
  return (*(a0 - 1)).iv2;
}

int g0(void) {
  I0 *a = alloca(sizeof(*a) * 4);
  a[2].iv0 = 5;
  a[2].iv1 = 7;
  a[2].iv2 = 11;
  return f0(a) * f1(a) * f2(&a[3]);
}
Restructure how the driver communicates information about the target Objective-C runtime down to the frontend: break this down into a single target runtime kind and version, and compute all the relevant information from that. This makes it relatively painless to add support for new runtimes to the compiler. Make the new -cc1 flag, -fobjc-runtime=blah-x.y.z, available at the driver level as a better and more general alternative to -fgnu-runtime and -fnext-runtime. This new concept of an Objective-C runtime also encompasses what we were previously separating out as the "Objective-C ABI", so fragile vs. non-fragile runtimes are now really modelled as different kinds of runtime, paving the way for better overall differentiation. As a sort of special case, continue to accept the -cc1 flag -fobjc-runtime-has-weak, as a sop to PLCompatibilityWeak. I won't go so far as to say "no functionality change", even ignoring the new driver flag, but subtle changes in driver semantics are almost certainly not intended. llvm-svn: 158793 2012-06-20 06:18:46 +00:00			`// RUN: %clang_cc1 -triple i386-apple-darwin9 -fobjc-runtime=macosx-fragile-10.5 -O3 -emit-llvm -o %t %s`
Fix pointer addressing and array subscripting of Objective-C interface types. - I broke this in the switch to representing interfaces with opaque types. - <rdar://problem/6822660> clang crashes on subscript of interface in 32-bit mode llvm-svn: 70009 2009-04-25 05:08:32 +00:00			`// RUN: grep 'ret i32 385' %t`

Use functions with prototypes when appropriate; NFC A significant number of our tests in C accidentally use functions without prototypes. This patch converts the function signatures to have a prototype for the situations where the test is not specific to K&R C declarations. e.g., void func(); becomes void func(void); This is the final batch of tests being updated to add prototypes, hopefully. 2022-02-24 15:27:07 -05:00			`void *alloca(unsigned);`
Fix pointer addressing and array subscripting of Objective-C interface types. - I broke this in the switch to representing interfaces with opaque types. - <rdar://problem/6822660> clang crashes on subscript of interface in 32-bit mode llvm-svn: 70009 2009-04-25 05:08:32 +00:00
			`@interface I0 {`
			`@public`
			`int iv0;`
			`int iv1;`
			`int iv2;`
			`}`
			`@end`

			`static int f0(I0 *a0) {`
			`return (*(a0 + 2)).iv0;`
			`}`

			`static int f1(I0 *a0) {`
			`return a0[2].iv1;`
			`}`

			`static int f2(I0 *a0) {`
			`return (*(a0 - 1)).iv2;`
			`}`

			`int g0(void) {`
			`I0 a = alloca(sizeof(a) * 4);`
			`a[2].iv0 = 5;`
			`a[2].iv1 = 7;`
			`a[2].iv2 = 11;`
			`return f0(a) * f1(a) * f2(&a[3]);`
			`}`