public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kazu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/17506] [4.0/4.1/4.2 regression] warning about uninitialized variable points to wrong location
Date: Mon, 28 Aug 2006 17:28:00 -0000 [thread overview]
Message-ID: <20060828172829.13619.qmail@sourceware.org> (raw)
In-Reply-To: <bug-17506-361@http.gcc.gnu.org/bugzilla/>
------- Comment #27 from kazu at gcc dot gnu dot org 2006-08-28 17:28 -------
The real fix it to issue "uninitialized warnings" before the inliner kicks in
but after we go into SSA, which is impossible until we start doing early SSA.
As Nathan suggests, this caveat should be mentioned in the release notes.
--
kazu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|kazu at gcc dot gnu dot org |unassigned at gcc dot gnu
| |dot org
Status|ASSIGNED |NEW
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17506
next prev parent reply other threads:[~2006-08-28 17:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-17506-361@http.gcc.gnu.org/bugzilla/>
2005-10-23 0:02 ` [Bug tree-optimization/17506] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-10-30 22:53 ` mmitchel at gcc dot gnu dot org
2005-10-30 23:40 ` steven at gcc dot gnu dot org
2006-02-24 0:31 ` [Bug tree-optimization/17506] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2006-05-12 13:42 ` rguenth at gcc dot gnu dot org
2006-05-25 2:32 ` mmitchel at gcc dot gnu dot org
2006-06-04 9:29 ` steven at gcc dot gnu dot org
2006-08-24 20:05 ` amylaar at gcc dot gnu dot org
2006-08-25 20:42 ` kazu at gcc dot gnu dot org
2006-08-28 17:28 ` kazu at gcc dot gnu dot org [this message]
2006-08-29 15:53 ` amylaar at gcc dot gnu dot org
2006-08-29 17:20 ` nathan at gcc dot gnu dot org
2006-08-30 3:33 ` [Bug tree-optimization/17506] [4.0/4.1 " pinskia at gcc dot gnu dot org
2006-08-30 18:47 ` amylaar at gcc dot gnu dot org
2006-08-30 18:58 ` amylaar at gcc dot gnu dot org
2006-10-18 9:27 ` rguenth at gcc dot gnu dot org
2007-02-14 9:03 ` mmitchel at gcc dot gnu dot org
2007-04-03 5:20 ` pinskia at gcc dot gnu dot org
2007-08-15 15:23 ` manu at gcc dot gnu dot org
2008-02-20 22:34 ` [Bug tree-optimization/17506] [4.0/4.1 Regression] " rguenth 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=20060828172829.13619.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).