Date: Sun, 1 Sep 2002 15:48:21 -0700 From: Will Andrews <will@csociety.org> To: current@FreeBSD.org, developers@FreeBSD.org Subject: Re: HEADS UP: GCC 3.2 in progress Message-ID: <20020901224821.GF2072@procyon.firepipe.net> In-Reply-To: <20020901222358.GA36579@dragon.nuxi.com> References: <20020901173956.7b23a223.ak03@gte.com> <20020901144645.A16984-100000@wonky.feral.com> <20020901215626.GA36167@dragon.nuxi.com> <20020901220034.GC2072@procyon.firepipe.net> <20020901222358.GA36579@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 01, 2002 at 03:23:58PM -0700, David O'Brien wrote: > This is the same as using RELENG_4_6 (ie, 4.6-SECURE) in something. We > get bug fixes (that must work on *all* supported GCC arches). The risk > is _well_ mitigated. > > Why is everyone second guessing Kan on this import??? It will be a > wonder if we get another import done by him. Oh, I think GCC 3.2.1 prerelease knocks the socks off 3.1 prerelease. But any time someone is using a FreeBSD -RELEASE, gcc -v should say "release" in it. That's just MHO. Part of the reason I say this is because the gcc31 port uses the release version and is not subject to the same bugs that the *prerelease* 3.1 compiler that was in -CURRENT was. regards, -- wca 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?20020901224821.GF2072>