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/forward-protocol-metadata-s...

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.1 KiB
Mathematica
Raw Normal View History

Specify target triple to fix the tests I committed in r360359 that are still failing. llvm-svn: 360363
2019-05-10 02:32:16 +08:00
// RUN: %clang_cc1 -triple x86_64-apple-darwin10 -fobjc-runtime=macosx-10.14 -emit-llvm -x objective-c %s -o - | FileCheck %s
Objective-C. Fixes a regression when figuring out linkage for metadata symbols for forward referenced protocols which are never defined. // rdar://16203115 llvm-svn: 202761
2014-03-04 05:53:57 +08:00
// rdar://16203115
@interface NSObject @end
[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
@protocol P0 @end
Objective-C. Fixes a regression when figuring out linkage for metadata symbols for forward referenced protocols which are never defined. // rdar://16203115 llvm-svn: 202761
2014-03-04 05:53:57 +08:00
@interface A : NSObject <P0>
+(Class) getClass;
@end
@implementation A
+(Class) getClass { return self; }
@end
int main() {
Protocol *P0 = @protocol(P0);
return 0;
}
[CodeGen][ObjC] Remove the leading 'l' from symbols for protocol metadata and protocol list The leading 'l' tells ld64 to remove the symbol name, which can make debugging difficult. rdar://problem/47256637 Differential Revision: https://reviews.llvm.org/D59234 llvm-svn: 356156
2019-03-14 23:17:37 +08:00
// CHECK: @"_OBJC_PROTOCOL_$_P0" = weak hidden global
// CHECK: @"_OBJC_LABEL_PROTOCOL_$_P0" = weak hidden global
[CodeGen][ObjC] Remove the leading `l_` from ObjC symbols and make private symbols in the __DATA segment internal. This prevents the linker from removing the symbol names. Keeping the symbols visible enables tools to collect various information about the symbols, for example, tools that discover whether or not a symbol gets dirtied. rdar://problem/48887111 Differential Revision: https://reviews.llvm.org/D61454 llvm-svn: 360359
2019-05-10 01:43:52 +08:00
// CHECK: @"_OBJC_CLASS_PROTOCOLS_$_A" = internal global
// CHECK: @"_OBJC_PROTOCOL_REFERENCE_$_P0" = weak hidden global
Make the test a bit stronger by showing what is added to llvm.used. llvm-svn: 203170
2014-03-07 06:02:16 +08:00
CodeGen: use `llvm.used` for ObjC protocols These symbols are supposed to be preserved even by the linker. Use the `llvm.used` to ensure that the symbols are not removed by DCE in the linker. This should be a no-op change on MachO since the symbols are annotated as `no_dead_strip`. llvm-svn: 323247
2018-01-24 03:35:51 +08:00
// CHECK: llvm.used = appending global [3 x i8*]
[CodeGen][ObjC] Remove the leading 'l' from symbols for protocol metadata and protocol list The leading 'l' tells ld64 to remove the symbol name, which can make debugging difficult. rdar://problem/47256637 Differential Revision: https://reviews.llvm.org/D59234 llvm-svn: 356156
2019-03-14 23:17:37 +08:00
// CHECK-SAME: "_OBJC_PROTOCOL_$_P0"
// CHECK-SAME: "_OBJC_LABEL_PROTOCOL_$_P0"
[CodeGen][ObjC] Remove the leading `l_` from ObjC symbols and make private symbols in the __DATA segment internal. This prevents the linker from removing the symbol names. Keeping the symbols visible enables tools to collect various information about the symbols, for example, tools that discover whether or not a symbol gets dirtied. rdar://problem/48887111 Differential Revision: https://reviews.llvm.org/D61454 llvm-svn: 360359
2019-05-10 01:43:52 +08:00
// CHECK-SAME: "_OBJC_PROTOCOL_REFERENCE_$_P0"
CodeGen: use `llvm.used` for ObjC protocols These symbols are supposed to be preserved even by the linker. Use the `llvm.used` to ensure that the symbols are not removed by DCE in the linker. This should be a no-op change on MachO since the symbols are annotated as `no_dead_strip`. llvm-svn: 323247
2018-01-24 03:35:51 +08:00
// CHECK: llvm.compiler.used = appending global [7 x i8*]
test: simplify the matching logic a bit (NFC) Use CHECK-SAME directives to simplify the test conditions a bit. This makes it easier to see what is being checked. NFC. llvm-svn: 323230
2018-01-24 01:57:04 +08:00
// CHECK-SAME: OBJC_CLASS_NAME_
// CHECK-SAME: OBJC_METH_VAR_NAME_
// CHECK-SAME: OBJC_METH_VAR_TYPE_
[CodeGen][ObjC] Remove the leading `l_` from ObjC symbols and make private symbols in the __DATA segment internal. This prevents the linker from removing the symbol names. Keeping the symbols visible enables tools to collect various information about the symbols, for example, tools that discover whether or not a symbol gets dirtied. rdar://problem/48887111 Differential Revision: https://reviews.llvm.org/D61454 llvm-svn: 360359
2019-05-10 01:43:52 +08:00
// CHECK-SAME: "_OBJC_$_CLASS_METHODS_A"
test: simplify the matching logic a bit (NFC) Use CHECK-SAME directives to simplify the test conditions a bit. This makes it easier to see what is being checked. NFC. llvm-svn: 323230
2018-01-24 01:57:04 +08:00
// CHECK-SAME: OBJC_CLASS_NAME_.1
[CodeGen][ObjC] Remove the leading `l_` from ObjC symbols and make private symbols in the __DATA segment internal. This prevents the linker from removing the symbol names. Keeping the symbols visible enables tools to collect various information about the symbols, for example, tools that discover whether or not a symbol gets dirtied. rdar://problem/48887111 Differential Revision: https://reviews.llvm.org/D61454 llvm-svn: 360359
2019-05-10 01:43:52 +08:00
// CHECK-SAME: "_OBJC_CLASS_PROTOCOLS_$_A"
test: simplify the matching logic a bit (NFC) Use CHECK-SAME directives to simplify the test conditions a bit. This makes it easier to see what is being checked. NFC. llvm-svn: 323230
2018-01-24 01:57:04 +08:00
// CHECK-SAME: "OBJC_LABEL_CLASS_$"
// CHECK-SAME: section "llvm.metadata"