This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Status of inclusion of Cygwin/MingW into Main GCC
- To: Uwe Bonnes <bon at elektron dot ikp dot physik dot tu-darmstadt dot de>
- Subject: Re: Status of inclusion of Cygwin/MingW into Main GCC
- From: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Date: Tue, 21 Mar 2000 12:13:14 -0600
- cc: cygwin at sourceware dot cygnus dot com
Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de> writes:
> Huch...
>
> Are you talking about plain gcc-2.95.2.tar.gz or a present develloper
> snapshot?
>
GCC for all x86-win32 targets is still evolving, and the changes that
we've made to gcc-2.95.x branch will NOT make it into the official gcc
release branch (the release branch is frozen for new features). Most
of these changes are incorporated into the mainline gcc, ie., the
development branch, and will show up in the next major release.
Since we provide full sources, and will provide full diffs if requested,
I don't see this as a problem. The alternative is of course to cripple
our gcc releases and only provide what's in the official gcc-2.95.2
release. That is not likely to happen.
The GCC sources you get from the Cygwin/Mingw/etc release is simply a
superset of what you get in official gcc-2.95.2 release. I use that to
build our 10 or so targets, and do test it for regression to make sure
we're not crippling other host/target combinations.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com