From owner-freebsd-stable Mon May 4 09:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26986 for freebsd-stable-outgoing; Mon, 4 May 1998 09:11:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tamago.synopsys.com (tamago.synopsys.com [146.225.8.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26977 for ; Mon, 4 May 1998 09:11:18 -0700 (PDT) (envelope-from jbuck@Synopsys.COM) Received: from javelin.synopsys.com (javelin.synopsys.com [146.225.100.38]) by tamago.synopsys.com (8.8.8/8.8.5) with ESMTP id JAA05647; Mon, 4 May 1998 09:09:23 -0700 (PDT) Received: from atrus.synopsys.com (atrus.synopsys.com [146.225.121.23]) by javelin.synopsys.com (8.8.8/8.8.8) with SMTP id JAA15409; Mon, 4 May 1998 09:10:05 -0700 (PDT) From: Joe Buck Received: by atrus.synopsys.com (SMI-8.6/SNPS-Sol2) id JAA18839; Mon, 4 May 1998 09:10:04 -0700 Message-Id: <199805041610.JAA18839@atrus.synopsys.com> Subject: Re: GCC To: pfeifer@dbai.tuwien.ac.at Date: Mon, 4 May 98 9:10:04 PDT Cc: freebsd-stable@FreeBSD.ORG, obrien@NUXI.com, egcs@cygnus.com In-Reply-To: ; from "Gerald Pfeifer" at May 3, 98 6:26 pm X-Mailer: ELM [version 2.3 PL11] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > In production shops, I've seen a lot more places go to gcc 2.8.1 > > than EGCS, so I feel gcc/g++ is better tested and stable. > > Guys like Joe Buck , author of the "FAQ for g++ > and libg++", happen to disagree: > > [EGCS 1.0.x] is considerably more stable than 2.8.1 and vastly > more stable than the gcc2 snapshots [...] My statement above applies to C++. For C, I'd say gcc 2.8.1 seems fine. Those of us on both lists who see the reports know that the egcs testing has been more thorough that the gcc 2.8.x testing. Also, because gcc 2.8.1 is missing some crucial backend fixes, I would be very cautious about shipping any C++ code that uses exceptions with 2.8.1. Those false warnings you get with -O and -Wall are due to gcc 2.8.1's faulty control flow analysis, and that faulty analysis is used as the basis of optimization. Of course, you can verify by careful testing that your code is not being misoptimized, but since there is a better option available you are better off using it. gcc -fno-exceptions for gcc 2.8.1 is probably fine. The scandal is that the story FSF has put out as to why gcc 2.8.x took so long had to do with exceptions -- and they *still* haven't gotten it right. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message