This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Compilation time (was Re: GCC 3.3)
- From: Mike Stump <mrs at apple dot com>
- To: Phil Edwards <phil at jaj dot com>
- Cc: Daniel Berlin <dberlin at dberlin dot org>, Matt Austern <austern at apple dot com>, Mark Mitchell <mark at codesourcery dot com>, "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, gcc at gcc dot gnu dot org, bkoz at redhat dot com
- Date: Tue, 29 Apr 2003 14:33:27 -0700
- Subject: Re: Compilation time (was Re: GCC 3.3)
On Tuesday, April 29, 2003, at 12:30 PM, Phil Edwards wrote:
I've added timing to the autocrasher. Look for "TIME::" followed by
real
(wall clock), user, and system seconds in the logs.
Please output it as
PERF: %f <arbitrary unique string that explains it>
Analysis tools can then key up on these lines. There should be one
line per number, and the number of such lines should be stable, and the
unique text should be stable.
The entire performance testsuite will follow this one standard, compile
time, generated code quality, size of generated code... Bigger ==
worse. units are arbitrary, but can be things like, seconds, bytes,
clock ticks, load stalls, cache misses...
Thanks.