From: Steven Bosscher <stevenb@suse.de>
To: law@redhat.com
Cc: gcc@gcc.gnu.org
Subject: An illustration of how bad the DOM memory regression is
Date: Sun, 19 Sep 2004 18:34:00 -0000 [thread overview]
Message-ID: <200409191908.18992.stevenb@suse.de> (raw)
Hi,
DOM at work on the test case for PR15524 cut off after case 15000
(ie. the original test case but halved) on an AMD64 box with 3GB
of RAM:
{GC 9944k -> 8041k} {GC 2291229k -> 14365k}
The full test case sends the machine to swapping land.
Just gross.
Gr.
Steven
reply other threads:[~2004-09-19 17:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200409191908.18992.stevenb@suse.de \
--to=stevenb@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.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).