From owner-freebsd-current Mon Sep 2 11:20:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FF4637B400; Mon, 2 Sep 2002 11:20:32 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC94743E72; Mon, 2 Sep 2002 11:20:31 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g82IKVFs048440; Mon, 2 Sep 2002 11:20:31 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g82IKVqd048439; Mon, 2 Sep 2002 11:20:31 -0700 (PDT) Date: Mon, 2 Sep 2002 11:20:31 -0700 From: "David O'Brien" To: Joe Marcus Clarke Cc: Sean Chittenden , current@FreeBSD.org Subject: Re: HEADS UP: GCC 3.2 in progress Message-ID: <20020902182031.GE18846@dragon.nuxi.com> Reply-To: current@FreeBSD.org Mail-Followup-To: David O'Brien , Joe Marcus Clarke , Sean Chittenden , current@FreeBSD.org References: <20020902021050.GE61993@ninja1.internal> <20020901222018.X8348-100000@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020901222018.X8348-100000@shumai.marcuscom.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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