Date: Mon, 2 Sep 2002 11:20:31 -0700 From: "David O'Brien" <dev-null@NUXI.com> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: Sean Chittenden <sean@FreeBSD.org>, current@FreeBSD.org Subject: Re: HEADS UP: GCC 3.2 in progress Message-ID: <20020902182031.GE18846@dragon.nuxi.com> In-Reply-To: <20020901222018.X8348-100000@shumai.marcuscom.com> References: <20020902021050.GE61993@ninja1.internal> <20020901222018.X8348-100000@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 01, 2002 at 10:21:13PM -0400, Joe Marcus Clarke wrote: > > > Actually, if 3.2 doesn't use thunks, it's likely to break Mozilla again. > > > This is really not that big of a deal. I'll just need to alter a patch, > > > and update the Mozilla people. > > > > My understanding from watching the patches move through mozilla is > > that the next release of mozilla _will_ work correctly with -CURRENT > > because it is aware of us not using thunks. The thunks patch for > > -CURRENT was verified in the mozilla src tree a week or two back. -sc > > Correct. However, if the compiler changes in -CURRENT not to use thunks, > then I need to adjust the local patch, and update the Mozilla bug. Our GCC 3.x now does the exact same thing GCC on Linux does. Why is this not a problem on Linux? 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?20020902182031.GE18846>