This is the mail archive of the
mailing list for the GCC project.
Re: Bootstrap failure on darwin 7.4.0 due to memory exhaution
- From: Chris Douty <christov at mac dot com>
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 13 Jul 2004 00:06:48 -0700
- Subject: Re: Bootstrap failure on darwin 7.4.0 due to memory exhaution
- References: <10407122257.AA14032@vlsi1.ultra.nyu.edu>
On Jul 12, 2004, at 3:57 PM, Richard Kenner wrote:
I had been watching Richard Kenner's patches and wanted to see how
things were progressing. Since Kenner had mentioned fixing ACATS
failures and this-and-such patch had broken Ada bootstrap
<http://gcc.gnu.org/ml/gcc/2004-07/msg00314.html> I thought that
was a good chance Ada *might* work now. Apparently not.
There are a few issues here:
(1) I have some fixes to Ada files in my tree that aren't in the FSF
because Arno and I are sorting out procedures to check things in while
still unable to run ACATS. Without one of these, I don't think Ada
bootstrap on *any* machine.
Ah. I hadn't quite clued into the fact that many patches were still in
your private tree.
(2) There was a recent change to the Ada front end that causes it to
variant records directly. This causes serious gimplification problems.
I *think* I've now fixed that, but am not sure.
(3) There is a bootstrap failure for Ada on x86 that RTH says is due to
major conceptual problems in assign_parms. He's working on it.
(4) Because testing of patches can't be done with Ada yet, several
recent patches have broken Ada so I'm very much in a "one step forward,
two steps behind" mode.
That's where I got confused (overeager?). I knew that you had a
"working" compiler, but I didn't know how much was not in the public
I'm trying to keep up and make some forward progress, but I've been
town for a few days (and will be out of town again next weekend) and
been slowing things down too.
The lowest failure rate so far for ACATS has been about 180 failures.
it's gone above that again now.
I wasn't expecting a *good* compiler, just something to test. :-)
Thank you very much for clarifying the situation and doubly to all of
you for your hard work.
Chris Douty <email@example.com>
"This is not a quotation."