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`).
9 lines
239 B
C++
9 lines
239 B
C++
// Test that we use the apple indexes.
|
|
// RUN: %clangxx %s -g -c -o %t --target=x86_64-apple-macosx -gdwarf-4
|
|
// RUN: lldb-test symbols %t | FileCheck %s
|
|
|
|
// CHECK: .apple_names index present
|
|
// CHECK: .apple_types index present
|
|
|
|
int foo;
|