This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: cc1 hog
- To: mrs at wrs dot com (Mike Stump)
- Subject: Re: cc1 hog
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 07 Oct 1997 10:50:28 -0600
- cc: egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199710012235.PAA01505@kankakee.wrs.com>you write:
> The right way to handle this is to introduce a new dejagnu reporting
> type, and use it, then add utilities to monitor and track those
> values.
>
> Something like:
>
> PERF: 400000000 gcc.c-torture/compile/900313-1.c, -O1 compvmsize
> PERF: 196.32 gcc.c-torture/compile/900313-1.c, -O1 comptime
> PERF: 47.1 gcc.c-torture/execute/900409-1.c compilation, -O0 runtime
>
> or more generally:
>
> PERF: %f %s
Yuk. I think this is far more complicated than it needs to be, and
it's probably unmanagable.
I'd be happy with something that just capped the amount of memory/time
any particular test needed -- the vast majority of c-torture tests are
small.
jeff