From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] gcc-4.6 warnings
Date: Thu, 25 Aug 2011 10:51:32 -0400 [thread overview]
Message-ID: <201108251051.33986.vapier@gentoo.org> (raw)
In-Reply-To: <7056F5B1-AD6C-459E-80F1-8EE436CC781A@kernel.crashing.org>
On Thursday, August 25, 2011 10:27:42 Kumar Gala wrote:
> On Aug 25, 2011, at 12:52 AM, Wolfgang Denk wrote:
> > Kumar Gala wrote:
> >>> If the variable is not used, why don't we remove it, then?
> >>
> >> In the vast number of cases it because of some #ifdef case not be
> >> defined in the given build.
> >
> > well, that's the reason for the warnings showing up, it isn't the
> > reason why we cannot fix these?
> :
> :), Thus my query if we really wanted to try and fix them by adding more
> :#ifdef's or live with that as an acceptable thing to do.
i feel like some (many?) #ifdef's in the tree could be done without ifdefs (by
relying on gcc's DCE) thus improving overall code quality
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110825/6669ba99/attachment.pgp
next prev parent reply other threads:[~2011-08-25 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 18:29 [U-Boot] gcc-4.6 warnings Kumar Gala
2011-08-24 18:47 ` Mike Frysinger
2011-08-24 19:05 ` Wolfgang Denk
2011-08-25 4:39 ` Kumar Gala
2011-08-25 5:52 ` Wolfgang Denk
2011-08-25 14:27 ` Kumar Gala
2011-08-25 14:51 ` Mike Frysinger [this message]
2011-08-25 19:50 ` Tabi Timur-B04825
2011-08-25 20:27 ` Mike Frysinger
2011-08-25 21:44 ` Timur Tabi
2011-08-25 21:45 ` Timur Tabi
2011-08-25 21:58 ` Mike Frysinger
2011-08-25 20:39 ` Wolfgang Denk
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=201108251051.33986.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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