From owner-cvs-all  Wed May  9  2:34: 6 2001
Delivered-To: cvs-all@freebsd.org
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by hub.freebsd.org (Postfix) with ESMTP
	id BBFB737B422; Wed,  9 May 2001 02:33:55 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA29854;
	Wed, 9 May 2001 19:33:41 +1000
Date: Wed, 9 May 2001 19:32:12 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@besplex.bde.org
To: Mikhail Teterin <mi@misha.privatelabs.com>
Cc: eric@FreeBSD.org, mi@aldan.algebra.com, knu@iDaemons.org,
	will@physics.purdue.edu, sobomax@FreeBSD.org, kris@obsecurity.org,
	kris@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: port policies
In-Reply-To: <200105082029.f48KTtC38076@misha.privatelabs.com>
Message-ID: <Pine.BSF.4.21.0105091924090.17145-100000@besplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 8 May 2001, Mikhail Teterin wrote:

> On  8 May, Eric Melville wrote:
> >> All/most optimizations are done to work better in the _average_ case,
> >> while  still working  acceptably in  the worst  cases. It  remains my
> >> believe, that  -j2 on  a single-CPU machine  will _always_  work, and
> >> on  _average_  will work  better.  I'll  be  interested in  seeing  a
> >> counter-example, but  I must  ask for NOT  mentioning Redmond  in any
> >> rebbutals.  Note,  that  simply  working slower  with  -j2  does  not
> >> qualify.

-j2 on a single-CPU machine with 2 disks (src on one, obj and root on the
other) was a little slower and consumed more resources for makeworld
the last time I checked.  It might be faster because the disk(s) are too
slow relative to the CPU and/or the VMIO cache is too small.  It's hard
to see how it could consume less resources.

> > Don't do things that the user didn't ask to be done.
> >
> > If the user  wants more excitment, we provide facilities  that make it
> > easy to do so.

-j2 in .MAKEFLAGS in the user's environment should be interesting enough.

> The  user did  not ask  for ``-O  -pipe'' in  the CFLAGS  either. -pipe,
> consumes  more  memory, while  -O  makes  compiling longer.  Should  the
> default CFLAGS be empty too? By your logic, they should...

CFLAGS should default to -O as specified by POSIX.  -pipe is an
implementation detail for one C compiler.  Forcing it breaks other C
compilers.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message