This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Speed regression from 3.2 to 3.3
- From: Pop Sébastian <pop at gauvain dot u-strasbg dot fr>
- To: Matt Austern <austern at apple dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 21 Jan 2003 01:04:54 +0100
- Subject: Re: Speed regression from 3.2 to 3.3
- References: <24AB274A-2CD1-11D7-8443-00039390D9E0@apple.com>
On Mon, Jan 20, 2003 at 03:44:40PM -0800, Matt Austern wrote:
>
> I find the gc regression to be particularly interesting. First, note
> that
> this can't be accounted for by the bug that Geoff fixed. Even if it
> applied to this test case, which it doesn't, Geoff fixed it in the 3.3
> release branch a week ago. So what can the gc regression mean?
> Logically, I can only think of two possibilities: either the gc
> algorithm
> suddenly got worse, or else the gc is now working on twice as much
> memory as it used to. Both possibilities are a bit hard to believe, but
> the second strikes me as far more plausible than the first.
>
You could try to reverse gc changes to its 3.2 version and look wether
time spent in gc decreases or not...