From: Robert Dewar <dewar@adacore.com>
To: Dave Korn <dave.korn@artimi.com>
Cc: 'Joe Buck' <Joe.Buck@synopsys.COM>,
'Dmitry Antipov' <antipov@dev.rtsoft.ru>,
gcc@gcc.gnu.org
Subject: Re: Dubious "'foo' might be used uninitialized in this function" message
Date: Wed, 15 Dec 2004 18:09:00 -0000 [thread overview]
Message-ID: <41C07DD7.2020404@adacore.com> (raw)
In-Reply-To: <NUTMEG4euumThMeOaIX0000076d@NUTMEG.CAM.ARTIMI.COM>
I also think it is fine if optimization *suppresses* warnings if
it can tell they are not needed. It is problematic if warnings
appear when you optimize, but if the alternative is not getting
the warnings at all, how is that better ???
next prev parent reply other threads:[~2004-12-15 18:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 15:23 Dmitry Antipov
2004-12-14 16:40 ` E. Weddington
2004-12-14 17:00 ` Nathan Sidwell
2004-12-15 9:00 ` Dmitry Antipov
2004-12-15 10:02 ` Nathan Sidwell
2004-12-15 12:06 ` Robert Dewar
2004-12-15 17:33 ` Joe Buck
2004-12-15 18:03 ` Dave Korn
2004-12-15 18:09 ` Robert Dewar [this message]
2004-12-15 17:33 ` Florian Weimer
2004-12-15 17:34 ` Robert Dewar
2004-12-15 17:52 ` Florian Weimer
2004-12-15 18:00 ` Robert Dewar
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=41C07DD7.2020404@adacore.com \
--to=dewar@adacore.com \
--cc=Joe.Buck@synopsys.COM \
--cc=antipov@dev.rtsoft.ru \
--cc=dave.korn@artimi.com \
--cc=gcc@gcc.gnu.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).