All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] gcc-4.6 warnings
Date: Thu, 25 Aug 2011 22:39:35 +0200	[thread overview]
Message-ID: <20110825203935.64C0E1222223@gemini.denx.de> (raw)
In-Reply-To: <7056F5B1-AD6C-459E-80F1-8EE436CC781A@kernel.crashing.org>

Dear Kumar Gala,

In message <7056F5B1-AD6C-459E-80F1-8EE436CC781A@kernel.crashing.org> you wrote:
> 
> > 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.

My experience is that hushing up GCC warnings is not really a good
idea.  First, you will then also fail to see when new code adds such
problems.  Second, there have been cases where warnings in one GCC
version because serious bugs in later versions, so we better fix them.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
It is a good thing for an uneducated man to read books of quotations.
                        - Sir Winston Churchill _My Early Life_ ch. 9

      parent reply	other threads:[~2011-08-25 20:39 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
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 [this message]

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=20110825203935.64C0E1222223@gemini.denx.de \
    --to=wd@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.