diff options
author | Martin Storsjö <martin@martin.st> | 2022-12-13 11:39:27 +0200 |
---|---|---|
committer | Martin Storsjö <martin@martin.st> | 2022-12-14 14:19:03 +0200 |
commit | 93c011eebbbb03ea5b7aa18b02870595d079fc8a (patch) | |
tree | 8a3f6aed2746d6a61bec93e6d577d1af2c59be22 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
parent | 10d34f5538e0d231a172608bdb7d08824771c7c7 (diff) | |
download | llvm-93c011eebbbb03ea5b7aa18b02870595d079fc8a.zip llvm-93c011eebbbb03ea5b7aa18b02870595d079fc8a.tar.gz llvm-93c011eebbbb03ea5b7aa18b02870595d079fc8a.tar.bz2 |
[OpenMP] Fix detecting warning options for GCC
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 warning spam like this, for every OpenMP source file that
produces build warnings with GCC:
cc1plus: warning: unrecognized command line option ‘-Wno-int-to-void-pointer-cast’
cc1plus: warning: unrecognized command line option ‘-Wno-return-type-c-linkage’
cc1plus: warning: unrecognized command line option ‘-Wno-covered-switch-default’
cc1plus: warning: unrecognized command line option ‘-Wno-enum-constexpr-conversion’
This matches how such warning options are detected and added in
llvm/cmake/modules/HandleLLVMOptions.cmake, e.g. like this:
check_cxx_compiler_flag("-Wclass-memaccess" CXX_SUPPORTS_CLASS_MEMACCESS_FLAG)
append_if(CXX_SUPPORTS_CLASS_MEMACCESS_FLAG "-Wno-class-memaccess" CMAKE_CXX_FLAGS)
This also matches how LLDB warning options were restructured for
GCC compatibility in e546bbfda0ab91cf78c096d8c035851cc7c3b9f3.
Differential Revision: https://reviews.llvm.org/D139922
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions