532dc62b90
This adds -no-opaque-pointers to clang tests whose output will change when opaque pointers are enabled by default. This is intended to be part of the migration approach described in https://discourse.llvm.org/t/enabling-opaque-pointers-by-default/61322/9. The patch has been produced by replacing %clang_cc1 with %clang_cc1 -no-opaque-pointers for tests that fail with opaque pointers enabled. Worth noting that this doesn't cover all tests, there's a remaining ~40 tests not using %clang_cc1 that will need a followup change. Differential Revision: https://reviews.llvm.org/D123115
35 lines
863 B
Objective-C
35 lines
863 B
Objective-C
// REQUIRES: x86-registered-target
|
|
// RUN: %clang_cc1 -no-opaque-pointers -triple x86_64-apple-darwin10 -S %s -o - | FileCheck %s
|
|
|
|
// rdar://9072317
|
|
|
|
/** The problem looks like clang getting confused when a single translation unit
|
|
contains a protocol with a property and two classes that implement that protocol
|
|
and synthesize the property.
|
|
*/
|
|
|
|
@protocol Proto
|
|
@property (assign) id prop;
|
|
@end
|
|
|
|
@interface NSObject @end
|
|
|
|
@interface Foo : NSObject <Proto> { int x; } @end
|
|
|
|
@interface Bar : NSObject <Proto> @end
|
|
|
|
@implementation Foo
|
|
@synthesize prop;
|
|
@end
|
|
|
|
@implementation Bar
|
|
@synthesize prop;
|
|
@end
|
|
|
|
// CHECK: _OBJC_$_INSTANCE_METHODS_Bar:
|
|
// CHECK-NEXT: .long 24
|
|
// CHECK-NEXT: .long 2
|
|
// CHECK-NEXT: .quad L_OBJC_METH_VAR_NAME_
|
|
// CHECK-NEXT: .quad L_OBJC_METH_VAR_TYPE_
|
|
// CHECK-NEXT: .quad "-[Bar prop]"
|