public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/53676] [4.7/4.8 regression] empty loop is not always removed now
Date: Thu, 14 Jun 2012 23:13:00 -0000 [thread overview]
Message-ID: <bug-53676-4-xGQl1rNYVC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53676-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53676
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-06-14
Target Milestone|--- |4.7.2
Summary|[4.7/4.8 regression] |[4.7/4.8 regression] empty
|constant folding |loop is not always removed
|regression, shown as |now
|slowdown as measured by |
|Adobe's C++Benchmark |
Ever Confirmed|0 |1
Severity|major |normal
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-06-14 23:13:14 UTC ---
Empty loop could get rid of the loop in previous versions of GCC. That was
replaced with cdce but that did not get rid of the empty loop. This is a minor
issue really because this benchmark is just making sure you got rid of an semi
empty loop.
next prev parent reply other threads:[~2012-06-14 23:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 22:47 [Bug middle-end/53676] New: [4.7/4.8 regression] constant folding regression, shown as slowdown as measured by Adobe's C++Benchmark matt at use dot net
2012-06-14 22:49 ` [Bug middle-end/53676] " matt at use dot net
2012-06-14 23:00 ` matt at use dot net
2012-06-14 23:13 ` pinskia at gcc dot gnu.org [this message]
2012-06-15 0:02 ` [Bug middle-end/53676] [4.7/4.8 regression] empty loop is not always removed now hjl.tools at gmail dot com
2012-06-19 13:18 ` rguenth at gcc dot gnu.org
2012-06-25 8:19 ` rguenth at gcc dot gnu.org
2012-06-25 13:41 ` rguenth at gcc dot gnu.org
2012-06-27 11:33 ` [Bug middle-end/53676] [4.7 " rguenth at gcc dot gnu.org
2012-06-27 11:33 ` rguenth at gcc dot gnu.org
2012-06-27 11:33 ` [Bug middle-end/53676] [4.7/4.8 " rguenth at gcc dot gnu.org
2012-06-27 18:27 ` [Bug middle-end/53676] [4.7 " matt at use dot net
2012-06-28 8:26 ` rguenther at suse dot de
2012-08-21 21:40 ` matt at use dot net
2012-08-22 8:48 ` rguenth at gcc dot gnu.org
2012-08-22 8:56 ` steven at gcc dot gnu.org
2012-08-22 9:18 ` rguenth at gcc dot gnu.org
2012-08-23 18:01 ` matt at use dot net
2012-09-06 15:21 ` rguenth at gcc dot gnu.org
2012-09-20 10:16 ` jakub at gcc dot gnu.org
2013-04-10 8:11 ` rguenth at gcc dot gnu.org
2013-04-11 7:59 ` rguenth at gcc dot gnu.org
2014-05-06 11:58 ` 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-53676-4-xGQl1rNYVC@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).