Lagom: Disable the unused-private-field warning on Lagom's clang builds

With the compilation of LibWeb, there's now quite a few cases where this
warning gets triggered. Rather than trying to fix them all right away,
we simply disable the warning for now.

This workaround was proposed by Andrew Kaster and BertalanD who promised
to open an issue about it!
This commit is contained in:
DexesTTP 2022-04-30 20:04:30 +02:00 committed by Linus Groh
parent 915ac9edd6
commit b388aa7876
Notes: sideshowbarker 2024-07-17 10:34:49 +09:00

View file

@ -102,6 +102,10 @@ endif()
if (CMAKE_CXX_COMPILER_ID MATCHES "Clang$") if (CMAKE_CXX_COMPILER_ID MATCHES "Clang$")
# Clang's default constexpr-steps limit is 1048576(2^20), GCC doesn't have one # Clang's default constexpr-steps limit is 1048576(2^20), GCC doesn't have one
add_compile_options(-Wno-overloaded-virtual -Wno-user-defined-literals -fconstexpr-steps=16777216) add_compile_options(-Wno-overloaded-virtual -Wno-user-defined-literals -fconstexpr-steps=16777216)
# FIXME: Re-enable this check when the warning stops triggering, or document why we can't stop it from triggering.
# For now, there is a lot of unused private fields in LibWeb that trigger this that could be removed.
# See issue #14137 for details
add_compile_options(-Wno-unused-private-field)
if (ENABLE_FUZZERS_LIBFUZZER) if (ENABLE_FUZZERS_LIBFUZZER)
add_compile_options(-fsanitize=fuzzer) add_compile_options(-fsanitize=fuzzer)