This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC
- To: obrien at NUXI dot com
- Subject: Re: GCC
- From: Jim Wilson <wilson at cygnus dot com>
- Date: Wed, 06 May 1998 15:17:42 -0700
- cc: "P. van Leeuwen" <pvl at nanoteq dot com>, "'law at cygnus dot com'" <law at cygnus dot com>, Joe Buck <jbuck at synopsys dot com>, "pfeifer at dbai dot tuwien dot ac dot at" <pfeifer at dbai dot tuwien dot ac dot at>, "freebsd-stable at FreeBSD dot ORG" <freebsd-stable at freebsd dot org>, "egcs at cygnus dot com" <egcs at cygnus dot com>
This has been fixed in the development branch since late March, but for
some reason wasn't brought into the "release" branch.
FYI `release branch' probably means something completely different to the
FreeBSD folks than the EGCS folks. This is perhaps why you are confused.
FreeBSD has a release branch and a development branch, and work progresses
on them in parallel.
EGCS has only a single source tree, the development tree, and releases are
branches from the development tree. There was a branch for the egcs-1.0.x
release, and there will be another branch for the egcs-1.1.x release soon.
There is no such thing as "the release branch" such as FreeBSD has, so there
is no point in asking us to add patches to it. However, since the FreeBSD
patches are in our development tree, they will automatically be in the next
release branch, for the egcs-1.1.x releases.
The patches aren't in the egcs-1.0.x release branch because that was frozen
months ago, and the patches came too late for that.
It appears 1.0.3 is a Linux-only release as it only address problems
Linux users had.
It addresses problems from one specific Linux distributor, which needed to
be fixed before egcs could be the primary compiler for their next CD-ROM
distribution. However, considering that several of the changes are bug fixes
in the x86 port, it would likely be just as useful to FreeBSD users also.
Jim