From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: bpf: format not a string literal
Date: Wed, 26 Jul 2023 10:08:43 +0930 [thread overview]
Message-ID: <ZMBrE70GncL0Jp/8@squeak.grove.modra.org> (raw)
* config/tc-bpf.c (md_assemble): Correct as_bad call.
diff --git a/gas/config/tc-bpf.c b/gas/config/tc-bpf.c
index c56b8fe984f..095b05ac7af 100644
--- a/gas/config/tc-bpf.c
+++ b/gas/config/tc-bpf.c
@@ -853,7 +853,7 @@ md_assemble (char *str ATTRIBUTE_UNUSED)
as_bad (_("unrecognized instruction `%s'"), str);
if (errmsg != NULL)
{
- as_bad (errmsg);
+ as_bad ("%s", errmsg);
free (errmsg);
}
--
Alan Modra
Australia Development Lab, IBM
reply other threads:[~2023-07-26 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZMBrE70GncL0Jp/8@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.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).