Re: PATCH TRUNK: better format output for time reports.

2011-06-25 Thread Eric Botcazou
> > Ok. > > Committed revision 175396. Please avoid posting messages like this. See http://gcc.gnu.org/svnwrite.html: "When you have checked in a patch exactly as it has been approved, you do not need to tell that to people -- including the approver. People interested in when a particular patc

Re: PATCH TRUNK: better format output for time reports.

2011-06-25 Thread Basile Starynkevitch
On Sat, 25 Jun 2011 11:38:20 +0200 Richard Guenther wrote: > > ### patch against trunk 175201 > > Index: gcc/timevar.c > > === > > --- gcc/timevar.c       (revision 175201) > > +++ gcc/timevar.c       (working copy) > > @@ -478,7

Re: PATCH TRUNK: better format output for time reports.

2011-06-25 Thread Richard Guenther
On Sat, Jun 25, 2011 at 8:40 AM, Basile Starynkevitch wrote: > Hello All, > > When cc1 report timing, the timing variable name has a too short width for df > reg dead/unused notes: > > Execution times (seconds) >  phase setup           :   0.00 ( 0%) usr   0.00 ( 0%) sys   0.01 ( 0%) wall   >  1

PATCH TRUNK: better format output for time reports.

2011-06-24 Thread Basile Starynkevitch
Hello All, When cc1 report timing, the timing variable name has a too short width for df reg dead/unused notes: Execution times (seconds) phase setup : 0.00 ( 0%) usr 0.00 ( 0%) sys 0.01 ( 0%) wall 1089 kB ( 1%) ggc trivially dead code : 0.02 ( 1%) usr 0.00 ( 0%) sys