diff options
| author | Raul Tambre <raul@tambre.ee> | 2025-10-30 23:18:32 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-30 23:18:32 +0200 |
| commit | 21041c92925faf529717d96279b6d8f20b17c70c (patch) | |
| tree | 8e832c87fa6128e98c6461e99cc28136be97c834 /lldb/source/Plugins/ScriptInterpreter/Python | |
| parent | 4174429c591e0eebadcb2bbf77ca4b5a8a5baa83 (diff) | |
| download | llvm-21041c92925faf529717d96279b6d8f20b17c70c.zip llvm-21041c92925faf529717d96279b6d8f20b17c70c.tar.gz llvm-21041c92925faf529717d96279b6d8f20b17c70c.tar.bz2 | |
[NFCI][lldb][test] Fix mismatched C/C++ substitutions (#165773)
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`).
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions