From owner-freebsd-current Tue Jun 25 14:18:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from gyros.marcuscom.com (209-211-150-2.scn-exhibitor.com [209.211.150.2]) by hub.freebsd.org (Postfix) with ESMTP id B592037B401 for ; Tue, 25 Jun 2002 14:16:12 -0700 (PDT) Received: from gyros.marcuscom.com (localhost [127.0.0.1]) by gyros.marcuscom.com (8.12.4/8.12.3) with ESMTP id g5PJmIc2005478 for ; Tue, 25 Jun 2002 15:48:19 -0400 (EDT) (envelope-from marcus@FreeBSD.org) Received: (from marcus@localhost) by gyros.marcuscom.com (8.12.4/8.12.4/Submit) id g5PIW6Ja000433; Tue, 25 Jun 2002 14:32:06 -0400 (EDT) X-Authentication-Warning: gyros.marcuscom.com: marcus set sender to marcus@FreeBSD.org using -f Subject: Re: GCC upgrade ? on -current From: Joe Marcus Clarke To: Sean Chittenden Cc: Sid Carter , current@FreeBSD.org In-Reply-To: <20020625010403.J30655@ninja1.internal> References: <20020625071455.GA42940@calvin.in.ibm.com> <20020625010403.J30655@ninja1.internal> Content-Type: multipart/mixed; boundary="=-l29VlMviUoiyPLAOE3Yu" X-Mailer: Ximian Evolution 1.0.7 Date: 25 Jun 2002 14:32:06 -0400 Message-Id: <1025029926.328.9.camel@gyros.marcuscom.com> Mime-Version: 1.0 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 --=-l29VlMviUoiyPLAOE3Yu Content-Type: text/plain Content-Transfer-Encoding: 7bit On Tue, 2002-06-25 at 04:04, Sean Chittenden wrote: > > Just a query. Is there anything stopping us from moving to the > > latest gcc on current ? Just curious. Cause mozilla won't compile > > with gcc from current and I have installed gcc from the ports just > > for that. > > I hacked together a really crude patch based on some info from Joe > Clark(e?). Dig through the archives from earlier this week and you > should find something. -sc I'm still waiting on someone to come back to me with alpha results, and I'll commit the patch. If you missed it, it's re-attached. Joe > > -- > Sean Chittenden > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > --=-l29VlMviUoiyPLAOE3Yu Content-Disposition: attachment; filename=xptc_platforms_unixish_x86.h.diff Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; name=xptc_platforms_unixish_x86.h.diff; charset=ISO8859-1 --- xpcom/reflect/xptcall/src/md/unix/xptc_platforms_unixish_x86.h.orig Fri= Jun 21 01:12:40 2002 +++ xpcom/reflect/xptcall/src/md/unix/xptc_platforms_unixish_x86.h Fri Jun = 21 01:41:51 2002 @@ -94,8 +94,16 @@ * gcc is that the system gcc defines __FreeBSD_cc_version. This variable * can also identify the period of time that 4.0-CURRENT used thunks. */ -#if defined(__FreeBSD_cc_version) && \ - (__FreeBSD_cc_version < 400002 || __FreeBSD_cc_version > 400003) + +/* It seems we need to use thunks in FreeBSD -CURRENT after gcc-3.1 was me= rged. + * This solves a problem wherein regxpcom and/or regchrome would seg fault + * after running for a while. This problem has also exhibited itself on=20 + * the alpha platform. Therefore, use thunks on all non-i386 versions of + * -stable and _all_ versions of -CURRENT that are using gcc-3.1. + */ +#if defined(__FreeBSD_cc_version) && defined(__i386__) && \ + (__FreeBSD_cc_version < 400002 || __FreeBSD_cc_version > 400003) && \ + (__FreeBSD_cc_version < 500003) #define CFRONT_STYLE_THIS_ADJUST #else #define THUNK_BASED_THIS_ADJUST --=-l29VlMviUoiyPLAOE3Yu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message