Date: Fri, 14 Aug 1998 11:31:14 -0600 From: Steve Passe <smp@csn.net> To: Kyle Mestery <mestery@winternet.com> Cc: Alfred Perlstein <bright@hotjobs.com>, current@FreeBSD.ORG Subject: Re: new compiler? Message-ID: <199808141731.LAA06318@Ilsa.StevesCafe.com> In-Reply-To: Your message of "Fri, 14 Aug 1998 09:47:46 CDT." <Pine.GSO.3.96.980814093744.24706A-100000@tundra.winternet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > On Fri, 14 Aug 1998, Alfred Perlstein wrote: > > > to support more recent C++ standards by default, do any core team members > > have a "favorite" compiler? i'm kinda interested in seeing if i can do > > anything to have 3.0 come out with a more current compiler and would like > > to know which to look at. (also considering the alpha port) > > > I would also like to see this happen, and would be willing to help make it > happen. > > > 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. > ... We have a fairly complex system running with 2.2.6, FreeBSD pthreads and g++28. We tried both the standard compiler and egcs, but neither would compile the complete project, let alone run. The biggest problem is in the area of c++ templates, g++28 will eat things the other 2 barfed on. We had to make one patch to gcc28 b4 building, and turn on the "GCC28_THREAD_AWARE" define in libc_r to fix the problem with dynamic chain handling. After this exceptions seem to work properly. My vote would be for gcc28. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808141731.LAA06318>