public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/54896] Some optimization slowness with GCC 4.7.2
Date: Wed, 10 Oct 2012 22:04:00 -0000 [thread overview]
Message-ID: <bug-54896-4-3XmWR7qNoj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54896-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54896
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2012-10-10
CC| |steven at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #1 from Steven Bosscher <steven at gcc dot gnu.org> 2012-10-10 22:04:29 UTC ---
Can you please attach the test case?
next prev parent reply other threads:[~2012-10-10 22:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 21:28 [Bug c/54896] New: " tammy at Cadence dot COM
2012-10-10 22:04 ` steven at gcc dot gnu.org [this message]
2012-10-10 22:09 ` [Bug c/54896] " tammy at Cadence dot COM
2012-10-10 22:51 ` [Bug c/54896] [4.7/4.8 Regression] " steven at gcc dot gnu.org
2012-10-11 14:08 ` rguenth at gcc dot gnu.org
2012-11-25 15:55 ` rguenth at gcc dot gnu.org
2012-12-03 15:50 ` [Bug middle-end/54896] " rguenth at gcc dot gnu.org
2012-12-03 15:51 ` rguenth at gcc dot gnu.org
2013-03-06 11:04 ` [Bug middle-end/54896] optimization slowness on large basic blocks steven at gcc dot gnu.org
2013-03-06 11:12 ` rguenther at suse dot de
2013-03-12 18:24 ` steven at gcc dot gnu.org
2013-03-13 9:53 ` rguenth at gcc dot gnu.org
2021-12-26 6:38 ` 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-54896-4-3XmWR7qNoj@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).