From: Luc Van Oostenryck Date: Fri, 22 May 2020 00:25:02 +0000 (+0200) Subject: sparse: allow '{ 0 }' to be used without warnings X-Git-Tag: v2.28.0-rc0~80^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1c96642326;p=thirdparty%2Fgit.git sparse: allow '{ 0 }' to be used without warnings In standard C, '{ 0 }' can be used as an universal zero-initializer. However, Sparse complains if this is used on a type where the first member (possibly nested) is a pointer since Sparse purposely wants to warn when '0' is used to initialize a pointer type. Legitimaly, it's desirable to be able to use '{ 0 }' as an idiom without these warnings [1,2]. To allow this, an option have now been added to Sparse: 537e3e2dae univ-init: conditionally accept { 0 } without warnings So, add this option to the SPARSE_FLAGS variable. Note: The option have just been added to Sparse. So, to benefit now from this patch it's needed to use the latest Sparse source from kernel.org. The option will simply be ignored by older versions of Sparse. [1] https://lore.kernel.org/r/e6796c60-a870-e761-3b07-b680f934c537@ramsayjones.plus.com [2] https://lore.kernel.org/r/xmqqd07xem9l.fsf@gitster.c.googlers.com Signed-off-by: Luc Van Oostenryck Signed-off-by: Junio C Hamano --- diff --git a/Makefile b/Makefile index 9804a0758b..c58b781105 100644 --- a/Makefile +++ b/Makefile @@ -1188,7 +1188,7 @@ PTHREAD_CFLAGS = # For the 'sparse' target SPARSE_FLAGS ?= -SP_EXTRA_FLAGS = +SP_EXTRA_FLAGS = -Wno-universal-initializer # For the 'coccicheck' target; setting SPATCH_BATCH_SIZE higher will # usually result in less CPU usage at the cost of higher peak memory.