From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Sherrill To: Jeffrey A Law Cc: Mike Stump , egcs@cygnus.com Subject: Re: cc1 hog Date: Tue, 07 Oct 1997 23:14:00 -0000 Message-id: References: <5039.876243028@hurl.cygnus.com> X-SW-Source: 1997-10/msg00304.html 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