This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] speedup timevar pushing/poping
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, "gcc-patches at gcc dot gnu dot org Patches" <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 30 Mar 2004 19:45:19 -0500
- Subject: Re: [PATCH] speedup timevar pushing/poping
- References: <66A2D635-8208-11D8-99F1-000393A6D2F2@physics.uc.edu> <firstname.lastname@example.org>
On Mar 30, 2004, at 03:05, Zack Weinberg wrote:
Andrew Pinski <email@example.com> writes:
* timevar.c (timevar_enable): Change from
(timevar_push): Rename to ...
(timevar_push_1): this and remove the
(timevar_pop): Rename to ...
(timevar_pop_1): this and remove the
* timevar.h (POP_TIMEVAR_AND_RETURN): Use do/while loops.
(timevar_pop): New macro.
(timevar_push): New macro.
This is probably OK, but could you post a compiler speed and binary
Okay I did some speed and size comparison on i686 (because my PPC
laptop's battery ran out and I had forgot to take my power supply
to school today).
Here is the results.
test before after percent
Speed, PR8361 -O3 57.27s 57.19 .1%
cc1 size 11278673 11287701 .09%
cc1plus 14245041 14258105 .08%
So it is small speed win on i686 (but I know it is more than that
on my laptop) while it is slight size increase.