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`).
6 lines
279 B
C++
6 lines
279 B
C++
// Test CommandObject is cleaned up even after commands fail due to not taking any argument.
|
|
// RUN: %clangxx_host -g %s -o %t
|
|
// RUN: %lldb -f %t -o "settings set interpreter.stop-command-source-on-error false" -s \
|
|
// RUN: %S/Inputs/cleanup.lldbinit
|
|
int main() { return 0; }
|