From owner-freebsd-stable Fri Apr 27 17:53:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2C6F537B423 for ; Fri, 27 Apr 2001 17:53:10 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3S0r7D14129; Fri, 27 Apr 2001 17:53:07 -0700 (PDT) Date: Fri, 27 Apr 2001 17:53:07 -0700 From: Alfred Perlstein To: User Witr Cc: stable@FreeBSD.ORG Subject: Re: Trouble with 4.3-RELEASE compiler Message-ID: <20010427175307.Q18676@fw.wintelcom.net> References: <20010427155725.L18676@fw.wintelcom.net> <200104280035.UAA11427@ns1.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104280035.UAA11427@ns1.rwwa.com>; from witr@rwwa.com on Fri, Apr 27, 2001 at 08:38:30PM -0400 X-all-your-base: are belong to us. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * User Witr [010427 17:35] wrote: > > bright@wintelcom.net said: > :-As far as I know FreeBSD doesn't support nor recommened compiling > :-things (especially large mission critical programs) with anything > :-higher than -O. > > Out of curiosity, how much potential performance is FreeBSD throwing > away by banning -O2 and -O3? To my naive eyes it would seem better > to light that candle (try fix the -O2 bug) than curse the darkness. > Assuming there is significant performance gain and there truly is only > one major -O2 bug. -O2 used to be considered "safe" didn't it? Not that I know of. You might want to bring up the bug fixing part with the GCC developers, they're more likely to be able to fix it. Be sure to read thier FAQ on submitting bug reports. -- -Alfred Perlstein - [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message