Re: Optimisation patch
On Thu, 23 Mar 2000, Kris Kennaway wrote: On Fri, 24 Mar 2000, Bruce Evans wrote: Yes. make.conf shouldn't even hint that globally changing CFLAGS is supported or good. Note that the suggested "most common use" has been bogus since -pipe was added to the default settings in rev.1.31 (1998/05/01) of sys.mk. Hmm. What is the correct way of compiling world with optimisation or other compiler settings? `make world'. Optimization is in the default settings (-O). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Optimisation patch
On Fri, 24 Mar 2000, Bruce Evans wrote: Hmm. What is the correct way of compiling world with optimisation or other compiler settings? `make world'. Optimization is in the default settings (-O). Fair enough - but how about platform-specific code generation settings, e.g. -march=pentium? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Optimisation patch
At 4:29 PM -0800 2000/3/24, Kris Kennaway wrote: `make world'. Optimization is in the default settings (-O). Fair enough - but how about platform-specific code generation settings, e.g. -march=pentium? Whatever the official position is, it should be documented in /etc/make.conf, and warnings should be exceptionally clear and the potential consequences laid out as being exceptionally dire, if one was so "adventurous" as to enable them by default for all compiles or to enable them for the process of making the kernel. There's no sense wasting everyone's time when you get a lot of "Doctor, doctor -- it hurts when I do this!" to which our reply is only going to be "So don't do that, you moron!" -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, [EMAIL PROTECTED]|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Optimisation patch
At 5:14 PM -0800 2000/3/24, Kris Kennaway wrote: Err, this thread started with a patch to do that, which is what we're currently discussing. Understood. I just didn't want to lose sight of the real goal of the proposed patch, and what led up to the proposed patch. -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, [EMAIL PROTECTED]|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Optimisation patch
On Thu, 23 Mar 2000, Chuck Robey wrote: 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. Right..I saw the discussion on -stable, and I think it would be a bad idea as well. gcc -O2 is a tool which isn't always broken (excepting alpha breakage), so we shouldn't limit its use in the general case. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Optimisation patch
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.conf2000/03/22 00:49:20 1.101 % +++ make.conf2000/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 [EMAIL PROTECTED] % % % % To Unsubscribe: send mail to [EMAIL PROTECTED] % with "unsubscribe freebsd-current" in the body of the message % % % %Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Optimisation patch
On Thu, 23 Mar 2000, Kris Kennaway wrote: Any objections to the following? 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 # Yes. make.conf shouldn't even hint that globally changing CFLAGS is supported or good. Note that the suggested "most common use" has been bogus since -pipe was added to the default settings in rev.1.31 (1998/05/01) of sys.mk. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Optimisation patch
On Fri, 24 Mar 2000, Bruce Evans wrote: Yes. make.conf shouldn't even hint that globally changing CFLAGS is supported or good. Note that the suggested "most common use" has been bogus since -pipe was added to the default settings in rev.1.31 (1998/05/01) of sys.mk. Hmm. What is the correct way of compiling world with optimisation or other compiler settings? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
