Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Mar 2000 21:38:30 -0700
From:      "Russell L. Carter" <rcarter@pinyon.org>
To:        Chuck Robey <chuckr@picnic.mat.net>
Cc:        Kris Kennaway <kris@FreeBSD.ORG>, current@FreeBSD.ORG
Subject:   Re: Optimisation patch 
Message-ID:  <20000324043830.1681F7F@pinyon.org>
In-Reply-To: Message from Chuck Robey <chuckr@picnic.mat.net>  of "Thu, 23 Mar 2000 18:39:30 EST." <Pine.BSF.4.21.0003231837170.47847-100000@picnic.mat.net> 

next in thread | previous in thread | raw e-mail | index | archive | help

Hi folks,

%On Thu, 23 Mar 2000, Kris Kennaway wrote:
%
%> Any objections to the following?
%
%I don't mind at all ... I was wondering about just taking out the ability
%to even USE -O2 in the compiler, but there're probably *some* non-kernel
%related reasons for using it, and we shouldn't block it at that
%point.  Not for FreeBSD, but for some users doing their own code on
%FreeBSD.

Wrong solution to the problem.  Don't even consider it.

Let me tell you a 4 line story:

Long long time ago a low level research guy with time to burn benchmarked 
*every* RISC system compiler option against *every* GNU compiler option and
determined that the GNU compiler was best.  Thus in 1992 a trusting
closed source default dude was converted to open source.

Right solution:

"Kernel behavior with optimization flags other than -O are strictly
unsupported!" prominantly displayed in make.conf and the various kernel config
option files.  The proposed patch below is too mild.

And then, the bike shed painting people have to be stamped down
some how, when the issue arises.

Russell

%> 
%> Index: make.conf
%> ===================================================================
%> RCS file: /home/ncvs/src/etc/defaults/make.conf,v
%> retrieving revision 1.101
%> diff -u -u -r1.101 make.conf
%> --- make.conf	2000/03/22 00:49:20	1.101
%> +++ make.conf	2000/03/23 23:33:13
%> @@ -9,7 +9,13 @@
%>  # You have to find the things you can put here in the Makefiles and 
%>  # documentation of the source tree.
%>  #
%> -# One, and probably the most common, use could be:
%> +# CFLAGS controls the compiler settings used when compiling C code.
%> +# Note that optimisation settings above -O (-O2, ...) are not recommended
%> +# or supported for compiling the world or the kernel - please revert any
%> +# nonstandard optimisation settings to "-O" before submitting bug reports
%> +# to the developers.
%> +# Note also that at this time the -O2 setting is known to produce BROKEN
%> +# CODE on the Alpha platform.
%>  #
%>  #CFLAGS= -O -pipe
%>  #
%> 
%> ----
%> In God we Trust -- all others must submit an X.509 certificate.
%>     -- Charles Forsythe <forsythe@alum.mit.edu>
%> 
%> 
%> 
%> To Unsubscribe: send mail to majordomo@FreeBSD.org
%> with "unsubscribe freebsd-current" in the body of the message
%> 
%
%----------------------------------------------------------------------------
%Chuck Robey            | Interests include C & Java programming, FreeBSD,
%chuckr@picnic.mat.net  | electronics, communications, and signal processing.
%
%New Year's Resolution:  I will not sphroxify gullible people into looking up
%fictitious words in the dictionary.
%----------------------------------------------------------------------------
%
%
%
%To Unsubscribe: send mail to majordomo@FreeBSD.org
%with "unsubscribe freebsd-current" in the body of the message
%




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?20000324043830.1681F7F>