llvm-project/clang/test/CodeGenObjCXX/message-reference.mm

// RUN: %clang_cc1 -x objective-c++ -triple x86_64-apple-darwin10 -fobjc-runtime=macosx-fragile-10.5 -emit-llvm -o - %s | FileCheck %s
// rdar://8604515

@interface I {}
-(unsigned int&)referenceCount;
@end

@interface MyClass
+(int)writeBlip:(I*)srcBlip;
@end

@implementation MyClass
+(int)writeBlip:(I*)srcBlip{
  return ([srcBlip referenceCount] == 0);
}
@end

// CHECK: [[T:%.*]] = call dereferenceable({{[0-9]+}}) i32* bitcast (i8* (i8*, i8*, ...)* @objc_msgSend
// CHECK: [[U:%.*]] = load i32, i32* [[T]]
// CHECK: [[V:%.*]] = icmp eq i32 [[U]], 0
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 14:18:46 +08:00			`// RUN: %clang_cc1 -x objective-c++ -triple x86_64-apple-darwin10 -fobjc-runtime=macosx-fragile-10.5 -emit-llvm -o - %s \| FileCheck %s`
IRGen. Fix IR when message returns reference type. // rdar://8604515. llvm-svn: 126869 2011-03-03 04:09:49 +08:00			`// rdar://8604515`

			`@interface I {}`
			`-(unsigned int&)referenceCount;`
			`@end`

			`@interface MyClass`
			`+(int)writeBlip:(I*)srcBlip;`
			`@end`

			`@implementation MyClass`
			`+(int)writeBlip:(I*)srcBlip{`
			`return ([srcBlip referenceCount] == 0);`
			`}`
			`@end`

Mark C++ reference parameters as dereferenceable Because references must be initialized using some evaluated expression, they must point to something, and a callee can assume the reference parameter is dereferenceable. Taking advantage of a new attribute just added to LLVM, mark them as such. Because dereferenceability in addrspace(0) implies nonnull in the backend, we don't need both attributes. However, we need to know the size of the object to use the dereferenceable attribute, so for incomplete types we still emit only nonnull. llvm-svn: 213386 2014-07-18 23:52:10 +08:00			`// CHECK: [[T:%.]] = call dereferenceable({{[0-9]+}}) i32 bitcast (i8* (i8, i8, ...)* @objc_msgSend`
Update Clang tests to handle explicitly typed load changes in LLVM. llvm-svn: 230795 2015-02-28 05:19:58 +08:00			`// CHECK: [[U:%.]] = load i32, i32 [[T]]`
Add a bunch of missing "CHECK" colons in tests. NFC. llvm-svn: 232237 2015-03-14 09:10:19 +08:00			`// CHECK: [[V:%.*]] = icmp eq i32 [[U]], 0`