public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/8361] [3.3/3.4/4.0 regression] C++ compile-time performance regression
Date: Sun, 06 Feb 2005 16:54:00 -0000 [thread overview]
Message-ID: <20050206165417.26573.qmail@sourceware.org> (raw)
In-Reply-To: <20021025133601.8361.gerald@pfeifer.com>
------- Additional Comments From steven at gcc dot gnu dot org 2005-02-06 16:54 -------
Considering the numbers from #44, #48, and #49, I think we can conclude
that we are back to the compile times GCC 3.0 used to have. It should
be noted that we have a significantly larger memory foot print though,
and some of the speedups (especially from GCC 3.2 to GCC 3.3) came from
smaller hacks to the GC system (collect less often, etc.). But then,
most people just use the compiler with -O[0123] and no fancy --params
and similar hacks, so from a user POV this bug really is fixed, mostly.
I'm not sure if it is useful to keep this bug open any longer.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8361
next prev parent reply other threads:[~2005-02-06 16:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021025133601.8361.gerald@pfeifer.com>
2003-10-16 2:39 ` [Bug optimization/8361] [3.3/3.4 " mmitchel at gcc dot gnu dot org
2003-12-29 16:23 ` steven at gcc dot gnu dot org
2004-01-02 2:31 ` giovannibajo at libero dot it
2004-01-14 3:22 ` pinskia at gcc dot gnu dot org
2004-01-21 18:28 ` [Bug optimization/8361] [3.3/3.4/3.5 " gerald at pfeifer dot com
2004-02-06 1:44 ` pinskia at gcc dot gnu dot org
2004-03-13 16:38 ` mmitchel at gcc dot gnu dot org
2004-06-18 23:39 ` [Bug rtl-optimization/8361] " mmitchel at gcc dot gnu dot org
2004-06-22 8:38 ` gerald at pfeifer dot com
2004-06-25 4:32 ` pinskia at gcc dot gnu dot org
2004-06-25 7:44 ` pinskia at gcc dot gnu dot org
2004-08-29 18:50 ` mmitchel at gcc dot gnu dot org
2004-09-15 10:13 ` [Bug rtl-optimization/8361] [3.3/3.4/4.0 " pinskia at gcc dot gnu dot org
2004-09-18 14:40 ` pinskia at gcc dot gnu dot org
2004-09-24 15:01 ` bonzini at gcc dot gnu dot org
2004-10-26 12:34 ` nathan at gcc dot gnu dot org
2004-10-26 13:34 ` gerald at pfeifer dot com
2004-10-26 13:37 ` pinskia at gcc dot gnu dot org
2004-10-30 19:30 ` mmitchel at gcc dot gnu dot org
2004-11-12 12:52 ` steven at gcc dot gnu dot org
2004-11-18 18:56 ` pinskia at gcc dot gnu dot org
2004-11-19 18:22 ` pinskia at gcc dot gnu dot org
2004-12-04 16:31 ` pinskia at gcc dot gnu dot org
2004-12-18 4:13 ` pinskia at gcc dot gnu dot org
2004-12-23 11:16 ` steven at gcc dot gnu dot org
2005-01-10 1:35 ` pinskia at gcc dot gnu dot org
2005-01-16 4:50 ` pinskia at gcc dot gnu dot org
2005-01-16 14:16 ` belyshev at depni dot sinp dot msu dot ru
2005-01-16 14:21 ` steven at gcc dot gnu dot org
2005-01-28 14:48 ` pinskia at gcc dot gnu dot org
2005-01-28 15:15 ` steven at gcc dot gnu dot org
2005-02-06 15:34 ` steven@gcc.gnu.org
2005-02-06 16:26 ` steven@gcc.gnu.org
2005-02-06 16:54 ` steven@gcc.gnu.org [this message]
2005-02-07 2:13 ` ghazi at gcc dot gnu dot org
2005-02-08 10:19 ` gerald at pfeifer dot com
2005-07-23 22:14 ` [Bug rtl-optimization/8361] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org
2005-09-18 19:17 ` pinskia at gcc dot gnu dot org
2005-09-18 19:27 ` pinskia at gcc dot gnu dot 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=20050206165417.26573.qmail@sourceware.org \
--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).