From: Joel Sherrill <joel@OARcorp.com>
To: Jeffrey A Law <law@cygnus.com>
Cc: Mike Stump <mrs@wrs.com>, egcs@cygnus.com
Subject: Re: cc1 hog
Date: Tue, 07 Oct 1997 23:14:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.971007153646.19846L-100000@vespucci.advicom.net> (raw)
In-Reply-To: <5039.876243028@hurl.cygnus.com>
On Tue, 7 Oct 1997, Jeffrey A Law wrote:
>
> 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.
The "universal" cap is useful and important. it may be enough for
c-torture but other freely available test suites may not be as good a
fit.
I have spent a lot of time running the Ada Compiler Validation suite over
the past year or so on CPU simulators. There is a fairly large
difference between the longest and shortest tests in this suite. I have
always regretted that I have had to use a single time/instruction limit
for all tests in the suite.
OTOH it does work and is simpler to manager. :)
--joel
next prev parent reply other threads:[~1997-10-07 23:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-01 15:35 Mike Stump
1997-10-07 11:41 ` Jeffrey A Law
1997-10-07 23:14 ` Torbjorn Granlund
1997-10-07 23:14 ` Joel Sherrill [this message]
1997-10-08 21:19 ` Jeffrey A Law
1997-10-09 9:26 ` Joel Sherrill
-- strict thread matches above, loose matches on Subject: below --
1997-10-01 10:23 Neal Becker
1997-10-01 11:14 ` Joe Buck
1997-10-01 12:12 ` Robert Lipe
1997-10-01 14:23 ` Joe Buck
1997-10-01 12:39 ` Jim Wilson
1997-10-01 12:40 ` Jim Wilson
1997-10-01 14:02 ` Joe Buck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.3.96.971007153646.19846L-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=mrs@wrs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).