upgrading to CURRENT from STABLE

2003-01-09 Thread Joe Laughlin
In the UPDATING file, the following is noted:

FreeBSD 5.0-CURRENT has many debugging features turned on, in
both the kernel and userland.  These features attempt to detect
incorrect use of system primitives, and encourage loud failure
through extra sanity checking and fail stop semantics.  They
also substantially impact system performance.  If you want to
do performance measurement, benchmarking, and optimization,
you'll want to turn them off.

How do I turn them off?

Thanks,
Joe


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: upgrading to CURRENT from STABLE

2003-01-09 Thread David Holm
On Thu, 9 Jan 2003 20:34:19 +0100
David Holm [EMAIL PROTECTED] wrote:

 You can find info on how to set maximum optimizations with gcc 3.2 here:
 http://www.freehackers.org/gentoo/gccflags/flag_gcc3opt.html

BTW, some of these flags will only work with gcc 3.1 and higher, so you won't be able 
to set
them until after you have upgraded to 5.0. But as I said, you don't want to set the 
when
compiling world and kernel anyway ;).

I usually have two sets of CFLAGS and CXXFLAGS in my make.conf, one which I use when 
compiling
world/kernel and one which I use for everything else. It's just a matter of moving two 
'#' when
switching, the lazy could even write a script =).


 
 On Thu, 09 Jan 2003 11:22:39 -0800
 Joe Laughlin [EMAIL PROTECTED] wrote:
 
  In the UPDATING file, the following is noted:
  
   FreeBSD 5.0-CURRENT has many debugging features turned on, in
   both the kernel and userland.  These features attempt to detect
   incorrect use of system primitives, and encourage loud failure
   through extra sanity checking and fail stop semantics.  They
   also substantially impact system performance.  If you want to
   do performance measurement, benchmarking, and optimization,
   you'll want to turn them off.
  
  How do I turn them off?
  
  Thanks,
  Joe
  
  
  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
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: upgrading to CURRENT from STABLE

2003-01-09 Thread David Holm
On Thu, 9 Jan 2003 20:34:19 +0100
David Holm [EMAIL PROTECTED] wrote:

 You can find info on how to set maximum optimizations with gcc 3.2 here:
 http://www.freehackers.org/gentoo/gccflags/flag_gcc3opt.html

I'm the master of forgetting to tell people important stuff =(.
You should not use -march=somearch, instead use this on a separate line:
CPUTYPE?=somearch 
 
 On Thu, 09 Jan 2003 11:22:39 -0800
 Joe Laughlin [EMAIL PROTECTED] wrote:
 
  In the UPDATING file, the following is noted:
  
   FreeBSD 5.0-CURRENT has many debugging features turned on, in
   both the kernel and userland.  These features attempt to detect
   incorrect use of system primitives, and encourage loud failure
   through extra sanity checking and fail stop semantics.  They
   also substantially impact system performance.  If you want to
   do performance measurement, benchmarking, and optimization,
   you'll want to turn them off.
  
  How do I turn them off?
  
  Thanks,
  Joe
  
  
  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
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: upgrading to CURRENT from STABLE

2003-01-09 Thread Hiroyuki CHIBA
Hi,

 On Thu, 09 Jan 2003 11:22:39 -0800,
Joe Laughlin [EMAIL PROTECTED] said
 about: upgrading to CURRENT from STABLE:

joe In the UPDATING file, the following is noted:
joe  FreeBSD 5.0-CURRENT has many debugging features turned on, in
joe  both the kernel and userland.  These features attempt to detect
joe  incorrect use of system primitives, and encourage loud failure
joe  through extra sanity checking and fail stop semantics.  They
joe  also substantially impact system performance.  If you want to
joe  do performance measurement, benchmarking, and optimization,
joe  you'll want to turn them off.
joe How do I turn them off?

The document says:
 This includes
  1)  various WITNESS-related kernel options,
  2)  INVARIANTS,
  3)  malloc debugging flags in userland, and
  4)  various verbose features in the kernel.

For 1), 2)
  You can find the comment as Debugging for use in -current in
  /usr/src/sys/i386/conf/GENERIC.

For 3)
  see TUNING in malloc(3)

For 4)
  You may find them in UPDATING items (newer than base system)
   or
  Other options may be found by sysctl -a , I think.

and read COMMON ITEMS at end of UPDATING.


Regards,

Hiroyuki CHIBA: [EMAIL PROTECTED][EMAIL PROTECTED]
 Security Solution Promoting Division, Hitachi,Ltd.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message