changeset 545:1fa6eca684e5

Silence spurious warning in lwcpp build GCC has a stupid-ass warning about snprintf() truncating its output if its return value isn't tested. But that's the bleeping point of snprintf() in the first place - that it will truncate its output. Why should I need to add completely pointless extra code to check a return value *that doesn't matter* in my specific use case just to shut up an overwrought warning. So disable the stupid-ass warning. Why, yes, I do have a strong opinion. Why do you ask?
author William Astle <lost@l-w.ca>
date Thu, 16 Mar 2023 16:02:01 -0600
parents f12c767c363e
children 80b21c6b4a6b
files Makefile
diffstat 1 files changed, 5 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/Makefile	Mon Nov 14 18:01:32 2022 -0700
+++ b/Makefile	Thu Mar 16 16:02:01 2023 -0600
@@ -44,7 +44,11 @@
 CPPFLAGS += -DPROGSUFFIX=$(PROGSUFFIX)
 LDFLAGS += -Llwlib -llw
 
-CFLAGS ?= -O3 -Wall -Wno-char-subscripts
+# The format truncation warnings are bleeping stupid when applied to
+# snprintf() and friends. I'm using snprintf() precisely to prevent
+# overflows and I don't care if the string is truncated, so why should
+# I need to test the return value? Bleeping stupid.
+CFLAGS ?= -O3 -Wall -Wno-char-subscripts -Wno-format-truncation
 
 MAIN_TARGETS := lwasm/lwasm$(PROGSUFFIX) \
 	lwlink/lwlink$(PROGSUFFIX) \