From fcdf335e093e245e384874254ec897c97430ccf2 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Mon, 25 Jun 2018 21:04:11 +0200 Subject: manywarnings: Don't enable -Wjump-misses-init warnings by default. * build-aux/gcc-warning.spec: Add -Wjump-misses-init. * m4/manywarnings.m4 (gl_MANYWARN_ALL_GCC(C)): Remove -Wjump-misses-init. --- build-aux/gcc-warning.spec | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'build-aux/gcc-warning.spec') diff --git a/build-aux/gcc-warning.spec b/build-aux/gcc-warning.spec index e2625ea9d7..c47298e93c 100644 --- a/build-aux/gcc-warning.spec +++ b/build-aux/gcc-warning.spec @@ -18,7 +18,7 @@ -Warray-bounds=<0,2> handled specially by gl_MANYWARN_ALL_GCC -Warray-temporaries fortran -Wassign-intercept objc/objc++ --Wc++-compat FIXME maybe? borderline. some will want this +-Wc++-compat only useful for code meant to be compiled by a C++ compiler -Wc++0x-compat c++ -Wc++11-compat c++ -Wc++14-compat c++ @@ -65,6 +65,7 @@ -Wintrinsic-shadow fortran -Wintrinsics-std fortran -Winvalid-offsetof c++ and objc++ +-Wjump-misses-init only useful for code meant to be compiled by a C++ compiler -Wlarger-than- gcc --help=warnings artifact -Wlarger-than= FIXME: choose something sane? -Wline-truncation fortran -- cgit v1.2.1