config.mak.dev: enable -Wunreachable-code

Having the compiler point out unreachable code can help avoid bugs, like the one discussed in: https://lore.kernel.org/git/20250307195057.GA3675279@coredump.intra.peff.net/ In that case it was found by Coverity, but finding it earlier saves everybody time and effort. We can use -Wunreachable-code to get some help from the compiler here. Interestingly, this is a noop in gcc. It was a real warning up until gcc 4.x, when it was removed for being too flaky, but they left the command-line option to avoid breaking users. See: https://stackoverflow.com/questions/17249934/why-does-gcc-not-warn-for-unreachable-code However, clang does implement this option, and it finds the case mentioned above (and no other cases within the code base). And since we run clang in several of our CI jobs, that's enough to get an early warning of breakage. We could enable it only for clang, but since gcc is happy to ignore it, it's simpler to just turn it on for all developer builds. Signed-off-by: Jeff King <peff@peff.net> [jc: squashed meson.build change sent by Patrick] Signed-off-by: Junio C Hamano <gitster@pobox.com>

Jeff King committed Mar 17, 2025 at 16:53 UTC 16f5d967e2267ea37cd29d7aee21994921b6b98c
2 files changed +2
config.mak.dev
+1
@@ -39,6 +39,7 @@ DEVELOPER_CFLAGS += -Wunused
39 DEVELOPER_CFLAGS += -Wvla
40 DEVELOPER_CFLAGS += -Wwrite-strings
41 DEVELOPER_CFLAGS += -fno-common
42 +DEVELOPER_CFLAGS += -Wunreachable-code
43
44 ifneq ($(filter clang4,$(COMPILER_FEATURES)),)
45 DEVELOPER_CFLAGS += -Wtautological-constant-out-of-range-compare
meson.build
+1
@@ -698,6 +698,7 @@ if get_option('warning_level') in ['2','3', 'everything'] and compiler.get_argum
698 '-Woverflow',
699 '-Wpointer-arith',
700 '-Wstrict-prototypes',
701 + '-Wunreachable-code',
702 '-Wunused',
703 '-Wvla',
704 '-Wwrite-strings',