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/36296] bogus uninitialized warning (loop representation, VRP missed-optimization) Date: Wed, 20 Nov 2013 00:55:00 -0000 [thread overview] Message-ID: <bug-36296-4-IAHtPp1bod@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-36296-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36296 Jeffrey A. Law <law at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |law at redhat dot com Resolution|--- |WORKSFORME --- Comment #25 from Jeffrey A. Law <law at redhat dot com> --- All tests included in this BZ were tested and work fine on the trunk.
next prev parent reply other threads:[~2013-11-20 0:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-36296-4@http.gcc.gnu.org/bugzilla/> 2013-04-17 8:40 ` vincent-gcc at vinc17 dot net 2013-04-17 9:19 ` manu at gcc dot gnu.org 2013-04-17 9:32 ` manu at gcc dot gnu.org 2013-04-17 9:37 ` manu at gcc dot gnu.org 2013-04-17 11:17 ` vincent-gcc at vinc17 dot net 2013-04-17 12:25 ` vincent-gcc at vinc17 dot net 2013-11-20 0:55 ` law at redhat dot com [this message] 2014-02-16 13:13 ` jackie.rosen at hushmail dot com 2008-05-22 7:28 [Bug c/36296] New: wrong warning about potential uninitialized variable zimmerma+gcc at loria dot fr 2008-08-19 2:34 ` [Bug middle-end/36296] bogus uninitialized warning (loop representation, VRP missed-optimization) manu at gcc dot gnu dot org 2008-12-25 3:03 ` pinskia at gcc dot gnu dot org 2009-02-02 23:44 ` av1474 at comtv dot ru 2009-02-03 0:28 ` 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=bug-36296-4-IAHtPp1bod@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: 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).