public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joona.kiiski at gmail dot com" <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: Sun, 11 Jan 2015 22:10:00 -0000	[thread overview]
Message-ID: <bug-64491-4-Pp5FK84sH4@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 #5 from joona.kiiski at gmail dot com ---
Thanks for confirming the problem, Joost!

* The original reporter stated that also 4.9 branch is affected, but I
haven't tested this myself. No idea about 4.8 branch.

* Latest gcc stable releases (4.7.4, 4.8.4, 4.9.2) compile Stockfish
without this warning, so I assume that they are not affected.

* For Stockfish, the generated code is correct (despite the wrong analysis
by GCC). However I'm aware that GCC can do some aggressive optimizations in
this area, so in other cases, who knows...


On Sat, Jan 10, 2015 at 4:49 PM, Joost.VandeVondele at mat dot ethz.ch <
gcc-bugzilla@gcc.gnu.org> wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64491
>
> Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|WAITING                     |NEW
>    Last reconfirmed|2015-01-04 00:00:00         |2015-1-10
>                  CC|                            |Joost.VandeVondele at mat
> dot ethz
>                    |                            |.ch
>             Summary|warning: loop exit may only |[5 Regression] incorrect
>                    |be reached after undefined  |warning: loop exit may
> only
>                    |behavior                    |be reached after undefined
>                    |                            |behavior
>       Known to fail|                            |5.0
>
> --- Comment #4 from Joost VandeVondele <Joost.VandeVondele at mat dot
> ethz.ch> ---
> The incorrect warning is confirmed.
>
> I wonder if this incorrect analysis could lead to wrong code generation.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>


  parent reply	other threads:[~2015-01-11 22:10 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 ` joona.kiiski at gmail dot com [this message]
2015-01-12  7:18 ` [Bug middle-end/64491] " 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
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-Pp5FK84sH4@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).