From 49d795b985a4f9fe94be918562be48720d1655ba Mon Sep 17 00:00:00 2001 From: Daniel Bertalan Date: Wed, 11 Aug 2021 15:50:27 +0200 Subject: [PATCH] Meta: Enable `nonnull-compare` warnings Previously, this was disabled because GCC flagged seemingly correct and well-defined code. This was however not the case because GCC implicitly marked some pointers non-null, even if we wanted to handle them ourselves, and deleted null checks on them. By re-introducing this warning, we will know if the compiler tries to discard our code again. --- CMakeLists.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index 2e0e0e1d810..c6b18bf0e83 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -253,7 +253,6 @@ add_compile_options(-Wimplicit-fallthrough) add_compile_options(-Wlogical-op) add_compile_options(-Wmisleading-indentation) add_compile_options(-Wmissing-declarations) -add_compile_options(-Wno-nonnull-compare) add_compile_options(-Wnon-virtual-dtor) add_compile_options(-Wno-unknown-warning-option) add_compile_options(-Wundef)