From: Michael Elizabeth Chastain <mec@shout.net>
To: ezannoni@redhat.com
Cc: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: my 6.0 todo list
Date: Fri, 18 Jul 2003 18:57:00 -0000 [thread overview]
Message-ID: <200307181857.h6IIv7w0003432@duracef.shout.net> (raw)
Elena Z writes:
> I'd like to add this to the list of gcc's we test. I hope I'll get a
> chance to do this soon. There is a public branch that is called
> tree-ssa-20020619-branch.
Okay, I tossed tree-ssa-20020619-branch into my scripts for the current
spin.
I have 128 megabytes of memory, and I've got a 175 megabyte cc1plus
running. It's swapping the crap out of my poor IDE disk!
The command is: xgcc libjava/interpreter.cc. Not that it matters. It's
been running for 90 minutes. I expect that it's spending most of its
time banking on the swap partition.
So, anyone who wants to play with the ssa branch, get a machine with 256
megabytes or more of memory (or maybe a 192 megabyte machine and don't
run X or anything else on it).
tree-ssa is going in the "do not care until after gdb 6.0 is release"
category for me.
Michael C
next reply other threads:[~2003-07-18 18:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 18:57 Michael Elizabeth Chastain [this message]
[not found] <200307171542.LAA13377@smtp.ott.qnx.com>
2003-07-18 13:00 ` Andrew Cagney
2003-07-18 22:54 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-07-17 16:50 Michael Elizabeth Chastain
2003-07-18 6:41 ` Michal Ludvig
2003-07-17 16:47 Michael Elizabeth Chastain
2003-07-17 14:35 Michael Elizabeth Chastain
2003-07-17 15:37 ` Michal Ludvig
2003-07-17 15:46 ` Elena Zannoni
2003-07-17 16:38 ` Daniel Jacobowitz
2003-07-16 23:38 Andrew Cagney
2003-07-17 15:42 ` Alain Magloire
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=200307181857.h6IIv7w0003432@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.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