Date: Fri, 22 Nov 2002 14:50:48 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Marc Recht <marc@informatik.uni-bremen.de>, Harald Arnesen <harald@skogtun.org>, David Schultz <dschultz@uclink.Berkeley.EDU>, David O'Brien <obrien@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG Subject: Re: gcc 3.2.1 release import? Message-ID: <3DDEB4C8.A06A7E32@mindspring.com> References: <55350000.1037811461@leeloo.intern.geht.de> <20021121041449.GA17530@dragon.nuxi.com> <20021121214614.GA6062@HAL9000.homeunix.com> <87bs4iczjd.fsf@basilikum.skogtun.org> <87590000.1037924015@leeloo.intern.geht.de> <3DDD7F10.BFED05F7@mindspring.com> <120820000.1037929067@leeloo.intern.geht.de> <3DDDCD32.6D74D775@mindspring.com> <20021122064625.GA12620@troutmask.apl.washington.edu> <3DDE1711.6B9606B4@mindspring.com> <20021122152947.GA14766@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote:
> > Supposedly, bringing in 3.2 was going to solve more problems
> > than it caused. It turns out the 4.x compiler, GCC 2.95.3,
> > also does not have an ICE as a result of compiling that code.
>
> You know the reason why 3.2 pre-release was brought into
> the tree, right? GCC has changed the C++ ABI between
> 3.1.1 and 3.2. If FreeBSD 5.0 shipped with 2.95.3, then
> 5.x would use 2.95.3 until 6.0 was released. Try getting
> support from the GCC folks for 2.95.3.
I'm well aware of that. I was merely pointing out that all
compiler versions have different bugs, and you might as well
suggest a known quantity instead of an unknown one, if your
sole goal in life is to avoid a particular internal compiler
error, instead of looking at all the code involved.
> I respect David's judgement about bringing 3.2.1 into the
> tree, but your statement above ("totally blown out...")
> suggests you don't follow GCC development. Several
> significant bugs were fixed between our pre-release version
> and 3.2.1.
I *understand* that they fixed several bugs that are present
in the pre-release, and they *hope* they didn't introduce any
new ones. Given their track record in this regard (e.g. the
internal compiler error in 3.2.1-prereelease that wasn't there
in 2.95.3), I have little faith in their "hope".
Unless someone is willing to stand up as a shield to personally
take the slings and arrows from any new compiler bugs, which
*might* range up to and including delaying the 5.0-RELEASE as
a result of it, after import and bmake, not compiling some
things that worked with 3.2.1-prerelease, it can wait until
after the 5.0-RELEASE.
As you yourself pointed out: the C++ ABI change is in already,
so it's no longer the substantial risk it used to be. Unless
there's another ABI change (which the advocates of importing
the prerelease assured us there would not be), then the only
thing that not updating breaks is the example code that was
posted, and I think we can all live with that until at least
the day after the 5.0-RELEASE. 8-).
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DDEB4C8.A06A7E32>