21041c9292
Most of the cases were where a C++ file was being compiled with the C substitution. There were a few cases of the opposite though. LLDB seems to be the only real culprit in the LLVM codebase for these mismatches. Rest of the LLVM presumably sticks at least language-specific options in the common substitutions making the mistakes immediately apparent. I found these by using Clang frontend configuration files containing language-specific options for both C and C++ (e.g. `-std=c2y` and `-std=c++26`).
20 lines
443 B
C++
20 lines
443 B
C++
// RUN: %clangxx %s -g -c -o %t --target=x86_64-apple-macosx
|
|
// RUN: lldb-test symbols --name=foo --find=function --function-flags=method %t | \
|
|
// RUN: FileCheck %s
|
|
|
|
// CHECK-DAG: name = "sbar::foo()", mangled = "_ZN4sbar3fooEv"
|
|
// CHECK-DAG: name = "ffbar()::sbar::foo()", mangled = "_ZZ5ffbarvEN4sbar3fooEv"
|
|
|
|
struct sbar {
|
|
void foo();
|
|
};
|
|
void sbar::foo() {}
|
|
|
|
void ffbar() {
|
|
struct sbar {
|
|
void foo() {}
|
|
};
|
|
sbar a;
|
|
a.foo();
|
|
}
|