Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<001201bf9392$e5612340$6d0f4dd1@TIMYX18EWDT6RQ>
From:	"Tim Prince" <tprince AT computer DOT org>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	include cygwin with gcc distribution?
Date:	Tue, 21 Mar 2000 16:09:27 -0800
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.2919.5600
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.5600

I doubt that the gcc maintainers would care to add cygwin. I don't know
what position rh/cygnus would take if there were such interest. I continue
to
report gcc snapshot bugs which come up under cygwin, but no one cares
to deal with them, even when the preprocessed output reproduces the bug
when running under linux.  With all the effort going into supporting ia64 on
linux, it seems no one has the time for bugs which don't arise directly from
standard linux distros under standard testsuite compiler options.  Standard
gcc "almost" supports cygwin, to the extent that I could fix it up in a few
minutes to build a snapshot, if I didn't have to work around ICE's by
trying various levels of optimization.

I myself have been so busy looking for employment that I haven't carried
out my unspoken threat to learn more about gcc/g++ internals.  That threat
is in danger of being replaced by a threat to work on g95.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -