public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nvachhar at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58377] spurious "may be used uninitialized" warning with -Og Date: Tue, 10 Sep 2013 19:46:00 -0000 [thread overview] Message-ID: <bug-58377-4-hiyMs2baWW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58377-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58377 Neil Vachharajani <nvachhar at google dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nvachhar at google dot com --- Comment #7 from Neil Vachharajani <nvachhar at google dot com> --- It seems like the whole problem is that the loop early exit goes through bb_6 which is the same path the back-edge goes through.
next prev parent reply other threads:[~2013-09-10 19:46 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-10 9:35 [Bug c++/58377] New: spurious "may be unused" " rbd at debian dot org 2013-09-10 10:02 ` [Bug c++/58377] " paolo.carlini at oracle dot com 2013-09-10 10:31 ` rbd at debian dot org 2013-09-10 10:40 ` rbd at debian dot org 2013-09-10 11:40 ` paolo.carlini at oracle dot com 2013-09-10 12:03 ` rguenth at gcc dot gnu.org 2013-09-10 15:57 ` [Bug c++/58377] spurious "may be used uninitialized" " davidxl at google dot com 2013-09-10 19:46 ` nvachhar at google dot com [this message] 2013-09-10 20:14 ` davidxl at google dot com 2013-09-10 20:23 ` davidxl at google dot com 2013-09-10 23:08 ` davidxl at google dot com 2013-09-11 8:25 ` rguenth at gcc dot gnu.org 2013-09-11 12:20 ` rguenth at gcc dot gnu.org 2013-09-11 12:23 ` rguenth at gcc dot gnu.org 2013-09-11 12:23 ` rguenth at gcc dot gnu.org 2013-09-12 13:21 ` rguenth 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-58377-4-hiyMs2baWW@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).