public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/24639] [meta-bug] bug to track all uninit variable issues
Date: Wed, 09 Nov 2005 00:02:00 -0000	[thread overview]
Message-ID: <20051109000256.10790.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24639-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from law at redhat dot com  2005-11-09 00:02 -------
Created an attachment (id=10181)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10181&action=view)
Proposed patch and new testcases

I'm not comfortable self-approving this patch; the option processing code is
totally new to me and I have no idea if I got it right.  And while I believe
the sense of -Wuninitialized is correct (no change in current behavior), I
don't think we have reached a consensus on that issue.

I will note that after reviewing all the PRs, by far the most common complaint
is false positives,  #2 is missing warnings, particularly for objects which
have had their address taken, #3 is missing warnings in unreachable/dead code
(which we can now detect with -Wuninitialized=2 using this patch).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639


  parent reply	other threads:[~2005-11-09  0:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 18:53 [Bug middle-end/24639] New: " pinskia at gcc dot gnu dot org
2005-11-02 18:59 ` [Bug middle-end/24639] " pinskia at gcc dot gnu dot org
2005-11-02 19:00 ` pinskia at gcc dot gnu dot org
2005-11-02 19:01 ` pinskia at gcc dot gnu dot org
2005-11-02 19:17 ` pinskia at gcc dot gnu dot org
2005-11-09  0:02 ` law at redhat dot com [this message]
2007-03-06 15:09 ` manu at gcc dot gnu dot org
2007-10-12  9:44 ` manu at gcc dot gnu dot org
2008-08-18 16:44 ` [Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues 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=20051109000256.10790.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).