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 bootstrap/52391] [4.7/4.8 regression] genattrtab almost 5X slower for m68k than in 4.6 and earlier releases
Date: Thu, 22 Mar 2012 08:44:00 -0000 [thread overview]
Message-ID: <bug-52391-4-vfD0iQhvgF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52391-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52391
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|4.7.0 |4.7.1
--- Comment #11 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-22 08:26:27 UTC ---
GCC 4.7.0 is being released, adjusting target milestone.
next prev parent reply other threads:[~2012-03-22 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 23:08 [Bug other/52391] New: [4.7 " mikpe at it dot uu.se
2012-02-27 9:32 ` [Bug other/52391] " rguenth at gcc dot gnu.org
2012-02-27 10:48 ` [Bug bootstrap/52391] " rguenth at gcc dot gnu.org
2012-02-27 20:44 ` jakub at gcc dot gnu.org
2012-02-27 21:52 ` mikpe at it dot uu.se
2012-02-27 23:04 ` steven at gcc dot gnu.org
2012-02-27 23:05 ` mikpe at it dot uu.se
2012-02-27 23:16 ` steven at gcc dot gnu.org
2012-02-27 23:35 ` jakub at gcc dot gnu.org
2012-02-28 0:38 ` steven at gcc dot gnu.org
2012-02-28 9:02 ` steven at gcc dot gnu.org
2012-03-22 8:44 ` rguenth at gcc dot gnu.org [this message]
2012-05-05 10:14 ` [Bug bootstrap/52391] [4.7/4.8 " steven at gcc dot gnu.org
2012-05-05 11:31 ` steven at gcc dot gnu.org
2012-05-06 22:02 ` steven at gcc dot gnu.org
2012-05-07 12:46 ` steven 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-52391-4-vfD0iQhvgF@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).