diff options
| author | Martin Storsjö <martin@martin.st> | 2025-10-10 18:17:31 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-10 18:17:31 +0300 |
| commit | 13784f7a4de4d33689aa517c0c45ac34ebd367e5 (patch) | |
| tree | 9005d1066a62ad3021b2c83d4461c3938d5b1307 /lldb/source/Plugins/ScriptInterpreter/Python/Interfaces | |
| parent | 31d260211a27a59788c6a00a3bf55df8e5047940 (diff) | |
| download | llvm-13784f7a4de4d33689aa517c0c45ac34ebd367e5.zip llvm-13784f7a4de4d33689aa517c0c45ac34ebd367e5.tar.gz llvm-13784f7a4de4d33689aa517c0c45ac34ebd367e5.tar.bz2 | |
[cmake] Unconditionally use -Wno-pass-failed with Clang (#162835)
Since 4feae05c6abda364a9295aecfa600d7d4e7dfeb6, most of the handling of
warning options was rewritten to add such options based on hardcoded
knowledge about what compilers support which options, and since which
versions. This avoids a number of configure time checks, speeding up the
cmake configuration.
This avoids erroneously adding this option with GCC, which doesn't
really support it.
If testing for a warning option like -Wno-<foo> with GCC, GCC won't
print any diagnostic at all, leading to the options being accepted
incorrectly. However later, if compiling a file that actually prints
another warning, GCC will also print warnings about these -Wno-<foo>
options being unrecognized.
This avoids extra warning spam like this, for every source file that
does produce warnings with GCC:
At global scope:
cc1plus: note: unrecognized command-line option ‘-Wno-pass-failed’ may have been intended to silence earlier diagnostics
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/Interfaces')
0 files changed, 0 insertions, 0 deletions
