Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Sun, 27 Jun 1999 18:44:06 -0400
From: Chris Faylor <cgf AT cygnus DOT com>
To: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
Cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Hey! A snapshot!
Message-ID: <19990627184406.A8416@cygnus.com>
References: <19990627172006 DOT A8388 AT cygnus DOT com> <199906272136 DOT QAA08646 AT mercury DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <199906272136.QAA08646@mercury.xraylith.wisc.edu>; from Mumit Khan on Sun, Jun 27, 1999 at 04:36:15PM -0500

On Sun, Jun 27, 1999 at 04:36:15PM -0500, Mumit Khan wrote:
>Chris Faylor <cgf AT cygnus DOT com> writes:
>> It looks like our gcc problems have been worked around so there is a new
>> 26-June-1999 snapshot available for the morbidly curious...
>
>Could you please explain a bit what these problems are/were and what
>workarounds are needed? 

I would if I could.  One problem was an internal compiler error when
compiling syscalls.cc.  Another was a "cc1 looping" problem when
compiling environ.cc and others.

I believe that both were due to internal Cygnus development that hadn't
hit EGCS yet, but I could be mistaken.

We received patches from g++ and gcc engineers that worked around the
problem.  They're awaiting review before being put into the main gcc
sources.

cgf