Meta: Disable -Warray-bounds and -Wstringop-overflow on GCC
Some checks are pending
CI / Lagom (arm64, Sanitizer_CI, false, macos-15, macOS, Clang) (push) Waiting to run
CI / Lagom (x86_64, Fuzzers_CI, false, ubuntu-24.04, Linux, Clang) (push) Waiting to run
CI / Lagom (x86_64, Sanitizer_CI, false, ubuntu-24.04, Linux, GNU) (push) Waiting to run
CI / Lagom (x86_64, Sanitizer_CI, true, ubuntu-24.04, Linux, Clang) (push) Waiting to run
Package the js repl as a binary artifact / build-and-package (arm64, macos-15, macOS, macOS-universal2) (push) Waiting to run
Package the js repl as a binary artifact / build-and-package (x86_64, ubuntu-24.04, Linux, Linux-x86_64) (push) Waiting to run
Run test262 and test-wasm / run_and_update_results (push) Waiting to run
Lint Code / lint (push) Waiting to run
Label PRs with merge conflicts / auto-labeler (push) Waiting to run
Push notes / build (push) Waiting to run

These generate what seems to be nonsense warnings on Function and
ByteBuffer; they *should* be investigated at some point, but they don't
provide anything useful at this point.
This commit is contained in:
Ali Mohammad Pur 2025-04-06 20:48:12 +02:00 committed by Ali Mohammad Pur
parent 0a958c8e16
commit 6b883c5ccb
Notes: github-actions[bot] 2025-04-08 12:02:27 +00:00

View file

@ -108,6 +108,11 @@ elseif (CMAKE_CXX_COMPILER_ID STREQUAL "GNU")
add_cxx_compile_options(-Wno-unqualified-std-cast-call)
add_cxx_compile_options(-Wvla)
# FIXME: These warnings trigger on Function and ByteBuffer in GCC (only when LTO is disabled...)
# investigate this and maybe reenable them if they're not false positives/invalid.
add_cxx_compile_options(-Wno-array-bounds)
add_cxx_compile_options(-Wno-stringop-overflow)
# FIXME: This warning seems useful but has too many false positives with GCC 13.
add_cxx_compile_options(-Wno-dangling-reference)
elseif (CMAKE_CXX_COMPILER_ID MATCHES "Clang$" AND CMAKE_CXX_SIMULATE_ID MATCHES "MSVC")