From: Joe Buck <jbuck@synopsys.com>
To: neal@ctd.comsat.com (Neal Becker)
Cc: egcs@cygnus.com
Subject: Re: cc1 hog
Date: Wed, 01 Oct 1997 11:14:00 -0000 [thread overview]
Message-ID: <199710011808.LAA28701@atrus.synopsys.com> (raw)
In-Reply-To: <E0xGSUO-0000v8-00@data.ctd.comsat.com>
> 970929 hppa1.1 hpux9.05
>
> Running /src/egcs-970929/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
> PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
> 3538 neal -5 0 83388K 42732K sleep 0:12 18.27% 16.34% cc1
>
> No wonder make check takes *forever*.
Perhaps we need to enhance dejagnu to add memory limits, and count tests
as failing if they exceed a certain amount of memory. Otherwise we won't
immediately notice when a change suddenly explodes the amount of memory
required.
next prev parent reply other threads:[~1997-10-01 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-01 10:23 Neal Becker
1997-10-01 11:14 ` Joe Buck [this message]
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
1997-10-01 15:35 Mike Stump
1997-10-07 11:41 ` Jeffrey A Law
1997-10-07 23:14 ` Joel Sherrill
1997-10-08 21:19 ` Jeffrey A Law
1997-10-09 9:26 ` Joel Sherrill
1997-10-07 23:14 ` Torbjorn Granlund
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=199710011808.LAA28701@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=neal@ctd.comsat.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).