Displaying 2 results from an estimated 2 matches for "clangxx".
2017 Sep 07
2
Status of debuginfo-tests
...al {
public:
~SVal() {}
const void* Data;
unsigned Kind;
};
void bar(SVal &v) {}
class A {
public:
void foo(SVal v) { bar(v); }
};
int main() {
SVal v;
v.Data = 0;
v.Kind = 2142;
A a;
a.foo(v);
return 0;
}
Then, you could have:
// posix/aggregate-indirect-arg.s
// RUN: %clangxx %target_itanium_abi_host_triple -O0 -g %i -c -o %t.o
// RUN: %clangxx %target_itanium_abi_host_triple %t.o -o %t.out
// RUN: %test_debuginfo %s %t.out
// Radar 8945514
// DEBUGGER: break 22
// DEBUGGER: r
// DEBUGGER: p v
// CHECK: ${{[0-9]+}} =
// CHECK: Data ={{.*}} 0x0{{(0*)}}
// CHECK: Kin...
2017 Sep 07
2
Status of debuginfo-tests
That's true, but it still requires the person writing the test to be
familiar with both formats. Also anything more trivial than dumping a
single local variable will probably run into even more issues.
For example, The expression parsers each have their own unique quirks, and
it might not always be easy to translate.
Besides all the format compatibility issues, there's the more general