Date: Fri, 9 Aug 2002 20:48:03 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Marc Recht <marc@informatik.uni-bremen.de> Cc: freebsd-current@FreeBSD.ORG, michaelnottebrock@gmx.net Subject: Re: Compiler error XFree86-Server Message-ID: <20020810034803.GA38315@dragon.nuxi.com> In-Reply-To: <20020809212632.3dab64c3.marc@informatik.uni-bremen.de> References: <20020806230045.3EFF72DD@nebula.anchoragerescue.org> <3D5127D3.2030601@gmx.net> <20020809043953.GC980@dragon.nuxi.com> <3D534D0F.704@gmx.net> <20020809081355.754aca33.marc@informatik.uni-bremen.de> <20020809144713.GA3531@dragon.nuxi.com> <20020809212632.3dab64c3.marc@informatik.uni-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 09, 2002 at 09:26:32PM +0200, Marc Recht wrote:
> > IMO going to 3.3 would be much better -- we can actually get our needs
> > better addressed as the compiler is still in development, but about to
> > head into code slush. We cannot affect GCC 3.2.1 too much due to it
> > being on a release branch, and point release.
>
> But the GCC 3.3 release is targeted after 5.0-RELEASE (for Dec 15).
Yes. But our 5.0-RELEASE is will non-polished; so I think having the
compiler in the same shape is OK if it means we can get bugs fixed and
our needs taken care of.
> is IMHO somewhat risky. gcc 3.2 is scheduled for early August, so there's
> time enough to import and test it. Maybe even for 3.2.1. And the C++
> ABI breakages/fixes will hapen with the 3.2 release...
Many IA-64, and AMD x86-64 bug fixes and improvements aren't merged back
to the 3.{1,2} branch.
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?20020810034803.GA38315>