From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Many unused variable warnings
Date: Thu, 15 Dec 2016 10:11:25 -0500 [thread overview]
Message-ID: <20161215151125.GF4248@bill-the-cat> (raw)
In-Reply-To: <CAK7LNAQyB-V6Or3sWTTcNDDVDJTHNqkWYOT=6EqK_tNAe-G-hQ@mail.gmail.com>
On Thu, Dec 15, 2016 at 12:55:36PM +0900, Masahiro Yamada wrote:
> Hi.
>
> The recent GCC versions catch unused variables.
>
> This makes build testing noisy.
>
> Of course, we could use old GCC when running Buildman,
> but it would be nicer to eliminate the root causes.
>
> I got the following when I recently ran Buildman with arm/aarch64 GCC 6.1.
What's more worrying to me is that we need to adapt our RSA using code
for openssl 1.1 which is the default in debian/unstable, which is the
easiest way to get gcc 6.1 toolchains. I might take a quick stab at
fixing some of the warnings, thanks for the reminder!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161215/d97205dd/attachment.sig>
next prev parent reply other threads:[~2016-12-15 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 3:55 [U-Boot] Many unused variable warnings Masahiro Yamada
2016-12-15 15:11 ` Tom Rini [this message]
2016-12-15 15:47 ` Marek Vasut
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=20161215151125.GF4248@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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