5fb5df9c83
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
37 lines
699 B
Objective-C
37 lines
699 B
Objective-C
// RUN: %clang_cc1 -triple x86_64 -fobjc-runtime=macosx-fragile-10.5 -emit-llvm -o - %s | FileCheck %s
|
|
|
|
struct s0 {
|
|
int x;
|
|
};
|
|
|
|
@interface C0
|
|
@property int x0;
|
|
@property _Complex int x1;
|
|
@property struct s0 x2;
|
|
@end
|
|
|
|
// Check that we get exactly the message sends we expect, and no more.
|
|
//
|
|
// CHECK: define void @f0
|
|
void f0(C0 *a) {
|
|
// CHECK: objc_msgSend
|
|
int l0 = (a.x0 = 1);
|
|
|
|
// CHECK: objc_msgSend
|
|
_Complex int l1 = (a.x1 = 1);
|
|
|
|
// CHECK: objc_msgSend
|
|
struct s0 l2 = (a.x2 = (struct s0) { 1 });
|
|
|
|
// CHECK: objc_msgSend
|
|
// CHECK: objc_msgSend
|
|
int l3 = (a.x0 += 1);
|
|
|
|
// CHECK: objc_msgSend
|
|
// CHECK: objc_msgSend
|
|
_Complex int l4 = (a.x1 += 1);
|
|
|
|
// CHECK-NOT: objc_msgSend
|
|
// CHECK: }
|
|
}
|