From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Andrew Burgess <aburgess@redhat.com>,
Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: [PATCH v2 3/5] sim: Suppress non-literal printf warning
Date: Sun, 25 Sep 2022 08:42:04 +0000 [thread overview]
Message-ID: <01dad5247fe31088813a45d200500a3ed2cdbce9.1664095312.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1664095312.git.research_trasio@irq.a4lg.com>
Clang generates a warning if the format string of a printf-like function is
not a literal ("-Wformat-nonliteral"). On the default configuration, it
causes a build failure (unless "--disable-werror" is specified).
However, non-literal format string is completely safe here.
We have "include/diagnostics.h" to suppress certain warnings only when
necessary. Because DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL can suppress
warnings when the format string of a printf-like function is not a literal,
this commit adds this macro (only where necessary) to suppress this warning.
sim/ChangeLog:
* common/sim-hw.c (hw_vabort): Suppress non-literal printf warning
by using DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL.
---
sim/common/sim-hw.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/sim/common/sim-hw.c b/sim/common/sim-hw.c
index cece5638bc9..36f355d2262 100644
--- a/sim/common/sim-hw.c
+++ b/sim/common/sim-hw.c
@@ -425,10 +425,13 @@ hw_vabort (struct hw *me,
strcat (msg, ": ");
strcat (msg, fmt);
/* report the problem */
+ DIAGNOSTIC_PUSH
+ DIAGNOSTIC_IGNORE_FORMAT_NONLITERAL
sim_engine_vabort (hw_system (me),
STATE_HW (hw_system (me))->cpu,
STATE_HW (hw_system (me))->cia,
msg, ap);
+ DIAGNOSTIC_POP
}
void
--
2.34.1
next prev parent reply other threads:[~2022-09-25 8:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 12:57 [PATCH 0/4] sim/common: Suppress warnings if built with Clang Tsukasa OI
2022-09-13 12:57 ` [PATCH 1/4] sim: Add ATTRIBUTE_PRINTF Tsukasa OI
2022-09-13 12:57 ` [PATCH 2/4] sim: Remove self-assignments Tsukasa OI
2022-09-13 12:57 ` [PATCH 3/4] sim: Make WITH_{TRACE,PROFILE}-based macros bool Tsukasa OI
2022-10-05 11:38 ` Andrew Burgess
2022-10-06 5:33 ` Tsukasa OI
2022-09-13 12:57 ` [PATCH 4/4] sim: Suppress non-literal printf warning Tsukasa OI
2022-10-05 11:45 ` Andrew Burgess
2022-10-06 5:39 ` Tsukasa OI
2022-10-23 12:22 ` Mike Frysinger
2022-10-24 10:50 ` Tsukasa OI
2022-09-25 8:42 ` [PATCH v2 0/5] sim: Suppress warnings if built with Clang Tsukasa OI
2022-09-25 8:42 ` [PATCH v2 1/5] sim: Remove self-assignments Tsukasa OI
2022-09-25 8:42 ` [PATCH v2 2/5] sim: Make WITH_{TRACE,PROFILE}-based macros bool Tsukasa OI
2022-09-25 8:42 ` Tsukasa OI [this message]
2022-09-25 8:42 ` [PATCH v2 4/5] sim: Check known getopt definition existence Tsukasa OI
2022-09-25 8:42 ` [PATCH v2 5/5] sim: Initialize pbb_br_* by default Tsukasa OI
2022-10-06 6:43 ` [PATCH v3 0/5] sim: Suppress warnings if built with Clang Tsukasa OI
2022-10-06 6:43 ` [PATCH v3 1/5] sim: Remove self-assignments Tsukasa OI
2022-10-11 14:21 ` Andrew Burgess
2022-10-11 14:29 ` Tsukasa OI
2022-10-06 6:43 ` [PATCH v3 2/5] sim: Make WITH_{TRACE,PROFILE}-based macros bool Tsukasa OI
2022-10-06 6:43 ` [PATCH v3 3/5] sim: Suppress non-literal printf warning Tsukasa OI
2022-10-11 14:22 ` Andrew Burgess
2022-10-06 6:43 ` [PATCH v3 4/5] sim: Check known getopt definition existence Tsukasa OI
2022-10-12 16:28 ` Tom de Vries
2022-10-12 17:03 ` Tsukasa OI
2022-10-12 17:08 ` Tom de Vries
2022-10-12 17:20 ` Tom de Vries
2022-10-13 9:50 ` Tsukasa OI
2022-10-23 12:16 ` Mike Frysinger
2022-10-27 2:02 ` Tsukasa OI
2023-01-03 3:12 ` Mike Frysinger
2023-01-03 8:47 ` Tsukasa OI
2022-10-06 6:43 ` [PATCH v3 5/5] sim: Initialize pbb_br_* by default Tsukasa OI
2022-10-11 14:20 ` [PATCH v3 0/5] sim: Suppress warnings if built with Clang Andrew Burgess
2022-10-11 16:40 ` Tom de Vries
2022-10-11 18:02 ` Tsukasa OI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01dad5247fe31088813a45d200500a3ed2cdbce9.1664095312.git.research_trasio@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).