@matheusbsbs / matheus-bagliano / commits / 1c96642326
Fork 0

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 <luc.vanoostenryck@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Luc Van Oostenryck committed May 22, 2020 at 02:25 UTC 1c966423263cf77bb3fd2d87df4537d31853b58f
1 file changed +1 -1
Makefile
+1 -1
@@ -1188,7 +1188,7 @@ PTHREAD_CFLAGS =
1188
1189 # For the 'sparse' target
1190 SPARSE_FLAGS ?=
1191 -SP_EXTRA_FLAGS =
1191 +SP_EXTRA_FLAGS = -Wno-universal-initializer
1192
1193 # For the 'coccicheck' target; setting SPATCH_BATCH_SIZE higher will
1194 # usually result in less CPU usage at the cost of higher peak memory.