public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/32395] false positive warning about use of uninitialized variable.
Date: Mon, 25 Jun 2007 22:56:00 -0000 [thread overview]
Message-ID: <20070625225629.31367.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32395-7667@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from pluto at agmk dot net 2007-06-25 22:56 -------
(In reply to comment #2)
> This is caused by two things, jump threading and inlining. If we jump thread
> more, we no longer get the warning which is what you are seeing in 4.2.1.
>
the latest gcc 4.2 also produces this warning.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32395
next prev parent reply other threads:[~2007-06-25 22:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 17:24 [Bug c++/32395] New: " pluto at agmk dot net
2007-06-18 17:25 ` [Bug c++/32395] " pluto at agmk dot net
2007-06-19 8:10 ` [Bug middle-end/32395] " pinskia at gcc dot gnu dot org
2007-06-24 15:54 ` pluto at agmk dot net
2007-06-25 22:56 ` pluto at agmk dot net [this message]
2007-06-25 22:57 ` pluto at agmk dot net
2007-08-22 15:44 ` manu at gcc dot gnu dot org
2007-08-22 15:54 ` pluto at agmk dot net
2007-08-22 16:48 ` manu at gcc dot gnu dot org
2007-08-22 18:36 ` pluto at agmk dot net
2007-09-25 14:24 ` pluto at agmk dot net
2007-09-27 0:58 ` manu at gcc dot gnu dot org
2007-09-27 4:07 ` bangerth at dealii dot org
2008-01-08 20:00 ` pluto at agmk dot net
2008-01-23 21:25 ` pluto at agmk dot net
2008-01-23 23:20 ` manu at gcc dot gnu dot org
2008-02-01 17:56 ` manu at gcc dot gnu dot org
2010-03-15 10:32 ` [Bug middle-end/32395] false uninitialized warning (huge testcase) pluto at agmk dot net
2010-03-15 13:40 ` manu at gcc dot gnu dot org
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=20070625225629.31367.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).