This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C compile time
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Dara Hazeghi <dhazeghi at yahoo dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, pinskia at physics dot uc dot edu
- Date: 19 Jun 2003 15:42:31 -0400
- Subject: Re: C compile time
- Organization: Red Hat Canada
- References: <20030619192116.89674.qmail@web41111.mail.yahoo.com>
On Thu, 2003-06-19 at 15:21, Dara Hazeghi wrote:
> 1) At this point, the SPEC testers are keeping track
> of runtime. We already have compile regression testers
> for the testsuite which automatically report
> regressions to the list. Should the same be done for
> compile-time, ie a compile time increase of more than
> 1% prompts a message to the list.
>
SPEC already uses a geometric mean when doing more than 1 run. The
problem with SPEC is that it uses wall-clock timers. Variations in the
1-4% range aren't uncommon (even if the compiler didn't change).
If the machine running SPEC happens to be doing something else at the
time, the results will be affected. Running SPEC in single-user mode is
not practical for an automated tester, so all you can do is -STOP
everything else and disallow logins.
You really need to examine trends in performance and do the detective
work. In theory, the SPEC testers are collecting everything necessary,
down to the daily diffs. But the process is time consuming, just the
same.
Diego.