From owner-freebsd-current Sat Aug 22 19:47:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08220 for freebsd-current-outgoing; Sat, 22 Aug 1998 19:47:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08201 for ; Sat, 22 Aug 1998 19:47:51 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA32617; Sun, 23 Aug 1998 12:16:40 +0930 (CST) Received: by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA32123; Sun, 23 Aug 1998 12:16:39 +0930 Date: Sun, 23 Aug 1998 12:16:38 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@mercury To: Mike Smith Cc: Alex , Alexander Sanda , wwoods@cybcon.com, freebsd-current@FreeBSD.ORG Subject: Re: gcc 2.8 In-Reply-To: <199808221719.RAA20220@dingo.cdrom.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Aug 1998, Mike Smith wrote: > > I'm using egcs from their anon cvs > > repository, and after building ELF libs and X (and all other X related > > goodies), egcs works wonderfully. I don't have any major cli C++ > > programs, so I didn't bother with building an ELF world. gdb seems to be > > the only stumbling block for me. > > Try building the rest of the world, and run with it for a few weeks. For what it's worth, I've been using egcs (-O2 -mpentium -march=pentium) to compile my kernel and all the compilable parts of the world for some time now (there are about 10 things which egcs can't compile at present). I haven't experienced any problems whatsoever with things misbehaving or crashing randomly; in fact at the moment my system is about the most stable it's been all year. When I encounter a suspicious problem with a utility, I'll usually try recompiling it with gcc to see if it might be a compiler problem - but all the problems so far have been to do with current itself. I don't know whether there's any benefit to be gained by doing what I'm doing but it does at least seem to work :-) > Agreed, we need better C++ support. But obtaining it at the price of > damaging the operating system itself is not a tradeoff I think any of > us would be happy with. For the record, most of the C++ stuff in the source tree is not compilable with egcs..from memory the other parts which I have to compile with gcc are due to extra compiler warnings which cause compilation to fail (i.e. warnings treated as errors), the lkms (egcs doesnt have -aout) and the biosboot stuff (exceeds maximum length). Kris > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message