From: Nick Clifton <nickc@redhat.com>
To: Luis Machado <luis.machado@arm.com>,
Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
Jeff Law <jeffreyalaw@gmail.com>,
binutils@sourceware.org
Subject: Re: RFC: readelf: Explain why LLVM bitcode files cannot be read
Date: Wed, 24 Aug 2022 10:24:13 +0100 [thread overview]
Message-ID: <17b1e73a-a73f-9bf4-4792-8150fb6d3d21@redhat.com> (raw)
In-Reply-To: <f5fe9522-dd84-c943-6d3e-7f9b3a8d52ef@arm.com>
Hi Luis,
>>> /home/rearnsha/gnusrc/gcc-cross/master/binutils/readelf.c:5738:6: error: format not a string literal and no format arguments [-Werror=format-security]
> I'm still seeing this for 32-bit Arm builds of binutils-gdb. Was the fix applied?
I believe so. Commit: b3ea2010cd06
Did I miss something ?
Cheers
Nick
next prev parent reply other threads:[~2022-08-24 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 14:20 Nick Clifton
2022-08-19 16:06 ` Jeff Law
2022-08-22 10:18 ` Nick Clifton
2022-08-23 15:26 ` Richard Earnshaw
2022-08-23 15:30 ` Nick Clifton
2022-08-23 20:35 ` Luis Machado
2022-08-24 9:24 ` Nick Clifton [this message]
2022-08-24 10:18 ` Luis Machado
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=17b1e73a-a73f-9bf4-4792-8150fb6d3d21@redhat.com \
--to=nickc@redhat.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=binutils@sourceware.org \
--cc=jeffreyalaw@gmail.com \
--cc=luis.machado@arm.com \
/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).