public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/46853] gcc fails to warn about uninitialized variable
Date: Thu, 09 Dec 2010 14:40:00 -0000	[thread overview]
Message-ID: <bug-46853-4-UdeEPEJ3Ko@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46853-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2010-12-09 14:40:12 UTC ---
(In reply to comment #3)
> It seems that the GCC devs do not take them all to heart.

No, they just don't have the resources to fix them all.  It's not an easy
problem.


  parent reply	other threads:[~2010-12-09 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 17:19 [Bug c/46853] New: " gcc-bugs at nospam dot pz.podzone.net
2010-12-08 20:35 ` [Bug c/46853] " rguenth at gcc dot gnu.org
2010-12-09  8:36 ` gcc-bugs at nospam dot pz.podzone.net
2010-12-09 14:36 ` d.g.gorbachev at gmail dot com
2010-12-09 14:40 ` redi at gcc dot gnu.org [this message]
2010-12-09 14:45 ` manu at gcc dot gnu.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=bug-46853-4-UdeEPEJ3Ko@http.gcc.gnu.org/bugzilla/ \
    --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).