public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/21733] bogus uninitialized warning (huge testcase)
Date: Mon, 09 Feb 2009 15:56:00 -0000	[thread overview]
Message-ID: <20090209155621.29179.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21733-1216@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from manu at gcc dot gnu dot org  2009-02-09 15:56 -------
This testcase is too big to see clearly what is going on. A reduced testcase
would be appreciated (preferably with just 1 function).


-- 

manu at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2005-11-26 07:39:55         |2009-02-09 15:56:21
               date|                            |
            Summary|filecmp.c:252: warning: #n1#|bogus uninitialized warning
                   |may be used uninitialized in|(huge testcase)
                   |this function               |


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


  parent reply	other threads:[~2009-02-09 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21733-1216@http.gcc.gnu.org/bugzilla/>
2005-11-26  7:39 ` [Bug middle-end/21733] filecmp.c:252: warning: #n1# may be used uninitialized in this function gdr at gcc dot gnu dot org
2005-11-26 16:53 ` pinskia at gcc dot gnu dot org
2006-08-26  3:52 ` pinskia at gcc dot gnu dot org
2008-08-20 11:33 ` manu at gcc dot gnu dot org
2009-02-09 15:56 ` manu at gcc dot gnu dot org [this message]
     [not found] <bug-21733-4@http.gcc.gnu.org/bugzilla/>
2013-11-20  0:49 ` [Bug middle-end/21733] bogus uninitialized warning (huge testcase) law at redhat dot com
2013-11-20  0:55 ` law at redhat dot com

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=20090209155621.29179.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).