From: Joe Buck <jbuck@synopsys.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Toon Moene <toon@moene.indiv.nluug.nl>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Daily snapshots of tree-ssa branch available
Date: Mon, 12 May 2003 17:04:00 -0000 [thread overview]
Message-ID: <20030512100142.A30772@synopsys.com> (raw)
In-Reply-To: <1052740725.27232.44.camel@frodo.toronto.redhat.com>; from dnovillo@redhat.com on Mon, May 12, 2003 at 08:43:54AM -0400
On Mon, May 12, 2003 at 08:43:54AM -0400, Diego Novillo wrote:
> Yes. This is an issue we need to fix before merging into mainline.
> GIMPLE tends to emit conditionals that trigger warnings like 'used
> before definition'. I believe that Jason was working on a change that
> would fix this.
Are these warnings valid, or is it the well-known problem that gcc can't
deal with
pointer* p;
bool flag = false;
if (expensive()) {
p = init_p();
flag = true;
}
do_something_else();
if (flag) {
use(p);
}
?
That is, gcc's uninitialized warning misses correlations between variables,
so this kind of thing gives a false warning at use(p).
next prev parent reply other threads:[~2003-05-12 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 15:18 Diego Novillo
2003-05-10 8:04 ` Toon Moene
2003-05-12 12:43 ` Diego Novillo
2003-05-12 17:04 ` Joe Buck [this message]
2003-05-13 14:52 ` Diego Novillo
2003-05-12 22:17 ` Toon Moene
2003-05-12 23:14 ` Diego Novillo
2003-05-13 20:32 ` Toon Moene
2003-05-14 12:46 ` Diego Novillo
2003-05-21 16:25 ` Jason Merrill
2003-05-22 6:03 ` Toon Moene
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=20030512100142.A30772@synopsys.com \
--to=jbuck@synopsys.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=toon@moene.indiv.nluug.nl \
/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).