public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64491] [5 Regression] incorrect warning: loop exit may only be reached after undefined behavior
Date: Wed, 18 Feb 2015 16:25:00 -0000	[thread overview]
Message-ID: <bug-64491-4-rDQvQGQnJm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64491-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Andrew Stubbs <ams at gcc dot gnu.org> ---
Just silencing the warning may not be enough. The compiler may optimize away
loop exit conditions based on this analysis. The warning mirrors the logic
rather than shares it (due to the way the logic is distributed) so this may not
actually be a problem, in this case, but I'd have to look closer.


  parent reply	other threads:[~2015-02-18 16:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04 20:24 [Bug c++/64491] New: " stuwph at live dot de
2015-01-04 20:46 ` [Bug c++/64491] " redi at gcc dot gnu.org
2015-01-10 15:58 ` joona.kiiski at iki dot fi
2015-01-10 16:04 ` joona.kiiski at iki dot fi
2015-01-10 16:49 ` [Bug c++/64491] [5 Regression] incorrect " Joost.VandeVondele at mat dot ethz.ch
2015-01-11 22:10 ` [Bug middle-end/64491] " joona.kiiski at gmail dot com
2015-01-12  7:18 ` Joost.VandeVondele at mat dot ethz.ch
2015-02-09  0:06 ` pinskia at gcc dot gnu.org
2015-02-18 13:57 ` jakub at gcc dot gnu.org
2015-02-18 16:25 ` ams at gcc dot gnu.org [this message]
2015-02-18 16:28 ` jakub at gcc dot gnu.org
2015-02-20 11:28 ` ams at gcc dot gnu.org
2015-02-24 17:01 ` ams at gcc dot gnu.org
2015-02-24 19:18 ` jakub at gcc dot gnu.org
2015-03-18 12:50 ` rguenth at gcc dot gnu.org
2015-03-18 12:53 ` jakub at gcc dot gnu.org
2015-03-18 14:27 ` ams at gcc dot gnu.org
2015-03-18 14:29 ` ams 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-64491-4-rDQvQGQnJm@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).