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 c++/40146] Unexplained "'<anonymous>' is used uninitialized in this function" warning Date: Mon, 11 Jan 2010 18:39:00 -0000 [thread overview] Message-ID: <20100111183903.14783.qmail@sourceware.org> (raw) In-Reply-To: <bug-40146-8961@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from manu at gcc dot gnu dot org 2010-01-11 18:39 ------- If this doesn't occur in GCC 4.5, the best we can do is to put the testcases in the testsuite and close this. Many things changed from 4.4. to 4.5 that may have cause the bug to disappear and that won't be backported, so even looking for them would be a waste of developer's time. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40146
next prev parent reply other threads:[~2010-01-11 18:39 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-14 13:09 [Bug c++/40146] New: " caolanm at redhat dot com 2009-05-14 13:09 ` [Bug c++/40146] " caolanm at redhat dot com 2009-05-14 14:32 ` pinskia at gcc dot gnu dot org 2009-08-25 13:54 ` bangerth at gmail dot com 2009-08-27 11:17 ` caolanm at redhat dot com 2009-08-27 11:20 ` caolanm at redhat dot com 2009-08-27 11:35 ` bangerth at gmail dot com 2009-09-10 17:44 ` shawn dot starr at rogers dot com 2009-09-10 18:15 ` pinskia at gcc dot gnu dot org 2009-09-10 18:19 ` pinskia at gcc dot gnu dot org 2009-10-16 11:06 ` gcc at abeckmann dot de 2009-10-16 13:11 ` gcc at abeckmann dot de 2010-01-10 22:01 ` matt at use dot net 2010-01-10 23:30 ` matt at use dot net 2010-01-11 18:39 ` manu at gcc dot gnu dot org [this message] 2010-07-13 14:37 ` caolanm at redhat dot com 2010-07-13 15:24 ` 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=20100111183903.14783.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: linkBe 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).