public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/52640] [4.8 Regression] performance bottleneck: gcc/tree.c;value_member
Date: Tue, 11 Dec 2012 09:59:00 -0000 [thread overview]
Message-ID: <bug-52640-4-v4bcd29MSu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52640-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52640
--- Comment #18 from Richard Biener <rguenth at gcc dot gnu.org> 2012-12-11 09:59:13 UTC ---
(In reply to comment #17)
> Any progress on this? Does the branch patch not work on the trunk?
Simply task of forward-porting and testing.
next prev parent reply other threads:[~2012-12-11 9:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 18:36 [Bug c/52640] New: " ncahill_alt at yahoo dot com
2012-03-21 0:04 ` [Bug c/52640] " jan.smets@alcatel-lucent.com
2012-03-21 0:44 ` steven at gcc dot gnu.org
2012-03-21 13:02 ` steven at gcc dot gnu.org
2012-03-21 13:03 ` steven at gcc dot gnu.org
2012-03-21 13:10 ` steven at gcc dot gnu.org
2012-03-21 15:57 ` jan.smets@alcatel-lucent.com
2012-03-21 16:21 ` steven at gcc dot gnu.org
2012-03-21 18:37 ` ncahill_alt at yahoo dot com
2012-03-21 18:37 ` [Bug middle-end/52640] [4.5/4.6/4.7/4.8 Regression] " steven at gcc dot gnu.org
2012-03-21 20:25 ` jan.smets@alcatel-lucent.com
2012-03-24 13:48 ` steven at gcc dot gnu.org
2012-03-24 13:49 ` steven at gcc dot gnu.org
2012-03-24 13:52 ` steven at gcc dot gnu.org
2012-03-24 14:48 ` [Bug middle-end/52640] [4.8 " steven at gcc dot gnu.org
2012-07-02 13:52 ` rguenth at gcc dot gnu.org
2012-09-07 11:11 ` rguenth at gcc dot gnu.org
2012-09-07 19:07 ` stevenb.gcc at gmail dot com
2012-12-11 8:04 ` jakub at gcc dot gnu.org
2012-12-11 9:59 ` rguenth at gcc dot gnu.org [this message]
2012-12-11 16:56 ` jan.smets@alcatel-lucent.com
2012-12-11 17:06 ` jakub at gcc dot gnu.org
2012-12-12 9:44 ` jakub at gcc dot gnu.org
2012-12-12 9:45 ` jakub 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-52640-4-v4bcd29MSu@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).