public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arsham at skrenes dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/59538] Optimization of -O2 or higher creates incorrect code in loop
Date: Tue, 17 Dec 2013 19:47:00 -0000 [thread overview]
Message-ID: <bug-59538-4-VkdhmElI1x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59538-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59538
Arsham Skrenes <arsham at skrenes dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #2 from Arsham Skrenes <arsham at skrenes dot com> ---
The result of the loop is implicitly used though (benchmarking how long it
takes to find nth prime number; I also use this code to create an artificial
workload for a graduate-level project). This is new behaviour by this version
of GCC. This is NOT a valid optimization as it clearly is having unintended
side-effects which I am showcasing.
next prev parent reply other threads:[~2013-12-17 19:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 19:31 [Bug c/59538] New: " arsham at skrenes dot com
2013-12-17 19:39 ` [Bug middle-end/59538] " pinskia at gcc dot gnu.org
2013-12-17 19:47 ` arsham at skrenes dot com [this message]
2013-12-17 21:13 ` pinskia at gcc dot gnu.org
2013-12-17 21:31 ` arsham at skrenes dot com
2013-12-17 22:28 ` dominiq at lps dot ens.fr
2013-12-18 1:24 ` arsham at skrenes dot com
2013-12-18 1:31 ` pinskia 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-59538-4-VkdhmElI1x@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).