ee6d3fa07e
As outlined in a previous RFC, the test/ASTMerge/Inputs folder is getting full and the tests are starting to become interdependent. This is undesirable because - it makes it harder to write new tests - it makes it harder to figure out at a glance what old tests are doing, and - it adds the risk of breaking one test while changing a different one, because of the interdependencies. To fix this, according to the conversation in the RFC, I have changed the layout from a.c Inputs/a1.c Inputs/a2.c to a/test.c a/Inputs/a1.c a/Inputs/a2.c for all existing tests. I have also eliminated interdependencies by replicating the input files for each test that uses them. https://reviews.llvm.org/D26571 llvm-svn: 287129
14 lines
1.1 KiB
Matlab
14 lines
1.1 KiB
Matlab
// RUN: %clang_cc1 -emit-pch -o %t.1.ast %S/Inputs/property1.m
|
|
// RUN: %clang_cc1 -emit-pch -o %t.2.ast %S/Inputs/property2.m
|
|
// RUN: not %clang_cc1 -ast-merge %t.1.ast -ast-merge %t.2.ast -fsyntax-only %s 2>&1 | FileCheck %s
|
|
|
|
// CHECK: property2.m:12:26: error: property 'Prop1' declared with incompatible types in different translation units ('int' vs. 'float')
|
|
// CHECK: property1.m:10:28: note: declared here with type 'float'
|
|
// CHECK: property2.m:12:26: error: instance method 'Prop1' has incompatible result types in different translation units ('int' vs. 'float')
|
|
// CHECK: property1.m:10:28: note: instance method 'Prop1' also declared here
|
|
// CHECK: property1.m:28:21: error: property 'Prop2' is synthesized to different ivars in different translation units ('ivar3' vs. 'ivar2')
|
|
// CHECK: property2.m:29:21: note: property is synthesized to ivar 'ivar2' here
|
|
// CHECK: property1.m:29:10: error: property 'Prop3' is implemented with @dynamic in one translation but @synthesize in another translation unit
|
|
// CHECK: property2.m:31:13: note: property 'Prop3' is implemented with @synthesize here
|
|
// CHECK: 4 errors generated.
|