When plugins are used the Multiplex(AST)Consumer is employed to dispatch to both the plugin ASTConsumers and the IRGen ASTConsumer. It wasn't dispatching a critical call for debug info, resulting in plugin users having a negative debugging experience. While I'm here, forward a bunch of other missing calls through the consumer that seem like they should be there. To test this, use the example plugin (requires plugins and examples) and split the test case up so that the plugin testing can be done under that requirement while the non-plugin testing will execute even in builds that don't include plugin support or examples. llvm-svn: 213213
50 lines
864 B
C++
50 lines
864 B
C++
|
|
// CHECK-DAG: [ DW_TAG_structure_type ] [PR16214] [line [[@LINE+1]], {{.*}} [def]
|
|
struct PR16214 {
|
|
int i;
|
|
};
|
|
|
|
typedef PR16214 bar;
|
|
|
|
bar *a;
|
|
bar b;
|
|
|
|
namespace PR14467 {
|
|
// CHECK-DAG: [ DW_TAG_structure_type ] [foo] [line [[@LINE+1]], {{.*}} [def]
|
|
struct foo {
|
|
};
|
|
|
|
foo *bar(foo *a) {
|
|
foo *b = new foo(*a);
|
|
return b;
|
|
}
|
|
}
|
|
|
|
namespace test1 {
|
|
// CHECK-DAG: [ DW_TAG_structure_type ] [foo] [line [[@LINE+1]], {{.*}} [def]
|
|
struct foo {
|
|
};
|
|
|
|
extern int bar(foo *a);
|
|
int baz(foo *a) {
|
|
return bar(a);
|
|
}
|
|
}
|
|
|
|
namespace test2 {
|
|
// FIXME: if we were a bit fancier, we could realize that the 'foo' type is only
|
|
// required because of the 'bar' type which is not required at all (or might
|
|
// only be required to be declared)
|
|
// CHECK-DAG: [ DW_TAG_structure_type ] [foo] [line [[@LINE+1]], {{.*}} [def]
|
|
struct foo {
|
|
};
|
|
|
|
struct bar {
|
|
foo f;
|
|
};
|
|
|
|
void func() {
|
|
foo *f;
|
|
}
|
|
}
|