From owner-freebsd-current Sun Aug 16 11:02:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02591 for freebsd-current-outgoing; Sun, 16 Aug 1998 11:02:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hen.scotland.net (phys-hen.scotland.net [194.247.64.128] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02586 for ; Sun, 16 Aug 1998 11:02:37 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from e1c2p7.scotland.net ([148.176.232.71] helo=timog.prestel.co.uk) by hen.scotland.net with esmtp (Exim 1.90 #5) for current@FreeBSD.org id 0z8778-00042q-00; Sun, 16 Aug 1998 19:01:10 +0100 Received: (qmail 25980 invoked by uid 1002); 16 Aug 1998 12:19:56 -0000 Message-ID: <19980816131955.A25942@prestel.co.uk> Date: Sun, 16 Aug 1998 13:19:55 +0100 From: Timo Geusch To: current@FreeBSD.ORG Subject: Re: new compiler? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Kyle Mestery on Fri, Aug 14, 1998 at 09:47:46AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 14, 1998 at 09:47:46AM -0500, Kyle Mestery wrote: > > gcc 2.8.1? (i've heard masses of people complain it's buggy) > > ecgs (not heard much... but i know it has some interesting optimizations > > for i386, and better C++ support) > > anything else? > > > I have heard the opposite. I have heard that egcs is buggy.:) On one of > the NetBSD lists, someone said the latest egcs release only compiles > decent code on ix86 and sparc platforms. And Terry has said before that > the way they handle threads is broken, because you must compile thread > support into the compiler. I haven't heard as many bad things about > gcc-2.8.1. Well, it seems to depend on the architecture that you are running on. I used the gcc28 port to build FreeBSD kernels on my box here and it works fine. At work, however, I'm running several Sparcs with OpenBSD 2.3 (which includes gcc 2.8.1 as default compiler). This compiler is REALLY buggy - there are lots of ways to make it barf with internal compiler errors, even on source code that compiles cleanly on a '386 gcc 2.8.1. So I guess YMMV, but I'd rather stay with 2.7.2.1 as default for the moment and have an additional gcc28 in my local tree just in case want/need it for C++ work. Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message