public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61409] [4.9/4.10 regression] -Wmaybe-uninitialized false-positive with -O2
Date: Wed, 25 Jun 2014 13:30:00 -0000	[thread overview]
Message-ID: <bug-61409-4-OkPAiczaMR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61409-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61409

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think what is important that if the other conditions besides mini_p != 0 are
not met, then control flow goes to basic blocks from which there is no path to
the bb with the use (in this testcase just to the return bb or empty blocks
that directly or indirectly fall thru into the return bb and the use is not in
the return bb).


  parent reply	other threads:[~2014-06-25 13:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  7:40 [Bug c/61409] New: [4.9 " eggert at gnu dot org
2014-06-04  9:29 ` [Bug c/61409] " manu at gcc dot gnu.org
2014-06-04  9:59 ` manu at gcc dot gnu.org
2014-06-04 10:31 ` [Bug middle-end/61409] [4.9/4.10 " rguenth at gcc dot gnu.org
2014-06-04 15:28 ` eggert at gnu dot org
2014-06-04 15:57 ` manu at gcc dot gnu.org
2014-06-25 13:26 ` jakub at gcc dot gnu.org
2014-06-25 13:30 ` jakub at gcc dot gnu.org [this message]
2014-06-26 12:45 ` rguenth at gcc dot gnu.org
2014-07-16 13:31 ` jakub at gcc dot gnu.org
2014-10-30 10:43 ` [Bug middle-end/61409] [4.9/5 " jakub at gcc dot gnu.org
2015-02-12 23:04 ` law at redhat dot com
2015-02-12 23:54 ` law at redhat dot com
2015-02-13  2:39 ` law at redhat dot com
2015-02-13  3:34 ` law at redhat dot com
2015-03-02 19:25 ` manu at gcc dot gnu.org
2015-06-26 20:09 ` [Bug middle-end/61409] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:35 ` jakub 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-61409-4-OkPAiczaMR@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).