llvm-project/clang/test/CodeGenObjC/forward-declare-protocol-gnu.m

// RUN: %clang -S -emit-llvm %s -o - -x objective-c -fobjc-runtime=gnustep-1.5 | FileCheck  %s

// Regression test: check that we don't crash when referencing a forward-declared protocol.
@protocol P;

@interface I <P>
@end

@implementation I

@end

// CHECK: @.objc_protocol
Revert "Revert r332955 "GNUstep Objective-C ABI version 2"" llvm-svn: 332963 2018-05-22 18:13:06 +08:00			`// RUN: %clang -S -emit-llvm %s -o - -x objective-c -fobjc-runtime=gnustep-1.5 \| FileCheck %s`

			`// Regression test: check that we don't crash when referencing a forward-declared protocol.`
			`@protocol P;`

[ObjC] Error out when using forward-declared protocol in a @protocol expression Clang emits invalid protocol metadata when a @protocol expression is used with a forward-declared protocol. The protocol metadata is missing protocol conformance list of the protocol since we don't have access to the definition of it in the compiled translation unit. The linker then might end up picking the invalid metadata when linking which will lead to incorrect runtime protocol conformance checks. This commit makes sure that Clang fails to compile code that uses a @protocol expression with a forward-declared protocol. This ensures that Clang does not emit invalid protocol metadata. I added an extra assert in CodeGen to ensure that this kind of issue won't happen in other places. rdar://32787811 Differential Revision: https://reviews.llvm.org/D49462 llvm-svn: 340102 2018-08-18 06:18:08 +08:00			`@interface I <P>`
			`@end`

			`@implementation I`

			`@end`
Revert "Revert r332955 "GNUstep Objective-C ABI version 2"" llvm-svn: 332963 2018-05-22 18:13:06 +08:00
			`// CHECK: @.objc_protocol`