From owner-freebsd-current Tue May 26 11:40:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24619 for freebsd-current-outgoing; Tue, 26 May 1998 11:40:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24584 for ; Tue, 26 May 1998 11:40:39 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA12914; Tue, 26 May 1998 18:40:34 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA16667; Tue, 26 May 1998 20:40:33 +0200 (MET DST) Message-ID: <19980526204032.01510@follo.net> Date: Tue, 26 May 1998 20:40:32 +0200 From: Eivind Eklund To: "John S. Dyson" Cc: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980526194334.44185@follo.net> <199805261749.MAA20256@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261749.MAA20256@dyson.iquest.net>; from John S. Dyson on Tue, May 26, 1998 at 12:49:52PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 12:49:52PM -0500, John S. Dyson wrote: > > On Tue, May 26, 1998 at 11:59:52AM -0500, John S. Dyson wrote: > > > I really don't think that we would want to also get into compiler > > > support issues. Tool support issues are complex enough. I can imagine > > > that egcs (could) be stable enough for our c++ compiler, but am much > > > less confident of it being our default c compiler. > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > be much better than GCC when you look at error control etc. > > > > Besides, it has the license we've got as a goal to have overall (ie, a > > BSD-style license :-) > > > Interesting idea... I wonder how good it's code generation is (what is > the cost of using it, performance wise???) If it isn't very slow, it > might be a more reliable alternative. I don't know how fast the compiled code is - from looking at what optimizations the compiler does, it looks like it should be as fast as or faster than GCC. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message