maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/CodeGenObjC/protocol-in-extended-class.m

30 lines
726 B
Mathematica
Raw Normal View History

clang/test: REQUIRES: s/x86-64-registered-target/x86-registered-target/ llvm-svn: 196350
2013-12-04 11:41:33 +08:00
// REQUIRES: x86-registered-target
Make -fobjc-nonfragile-abi the -cc1 default, since it's the increasingly prevailing case to the point that new features like ARC don't even support the fragile ABI anymore. This required a little bit of reshuffling with exceptions because a check was assuming that ObjCNonFragileABI was only being set in ObjC mode, and that's actually a bit obnoxious to do. Most, though, it involved a perl script to translate a ton of test cases. Mostly no functionality change for driver users, although there are corner cases with disabling language-specific exceptions that we should handle more correctly now. llvm-svn: 140957
2011-10-02 09:16:38 +08:00
// RUN: %clang_cc1 -triple x86_64-apple-darwin10 -S %s -o %t-64.s
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 20:51:05 +08:00
// RUN: FileCheck -check-prefix CHECK-LP64 --input-file=%t-64.s %s
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 -triple i386-apple-darwin -fobjc-runtime=macosx-fragile-10.5 -S %s -o %t-32.s
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 20:51:05 +08:00
// RUN: FileCheck -check-prefix CHECK-LP32 --input-file=%t-32.s %s
Patch to implement Protocols on class extensions. <rdar://problem/7269631> Protocols on class extensions don't work llvm-svn: 83322
2009-10-06 04:41:32 +08:00
@protocol MyProtocol
@end
@protocol ExtendedProtocol
@end
@interface ItDoesntWork<MyProtocol> {
}
-(void) Meth;
@end
@interface ItDoesntWork() <MyProtocol, ExtendedProtocol>
@end
@implementation ItDoesntWork
-(void) Meth {
ItDoesntWork <MyProtocol, ExtendedProtocol> *p = 0;
}
@end
// CHECK-LP64: l_OBJC_PROTOCOL_$_ExtendedProtocol:
// CHECK-LP32: L_OBJC_PROTOCOL_ExtendedProtocol: