public inbox for
 help / color / mirror / Atom feed
From: Alexandre Petit-Bianco <>
Subject: Re: compiler failure
Date: Thu, 25 Oct 2001 09:36:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Anthony Green writes:
> FYI.. With last night's compiler...

Interesting. I'm seeing strange things with the compiler these
days. When my machine's load gets past a certain point, I get into an
endless loop with a xerces file (I just got that with my nightly
tests.) When I try to build the file by hand, it works all the
time. This could be a GC bug -- like the FE not registering something
that eventually gets reclaimed, or it could be something else.

I couldn't reproduce the problem you described, but my compiler is from
yesterday morning :-(


      parent reply	other threads:[~2001-10-25  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25  8:00 Anthony Green
2001-10-25  9:28 ` Tom Tromey
2001-10-25  9:36 ` Alexandre Petit-Bianco [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).