Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Apr 2005 14:05:00 +0200 (CEST)
From:      Piotr Gnyp <toread@discordia.pl>
Cc:        questions@freebsd.org
Subject:   Re: make.conf question
Message-ID:  <20050411140326.V75661@discordia.pl>
In-Reply-To: <20050411093328.GA18884@xor.obsecurity.org>
References:  <20050411111418.J998@discordia.pl> <20050411093328.GA18884@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 11 Apr 2005, Kris Kennaway <kris@obsecurity.org> wrote:

> The version of gcc that comes with FreeBSD 4.x can't do better than
> this, i.e. it doesn't know about optimizations for newer CPUs.  In
> practise this isn't important.

Ok, so why this:
# The CPUTYPE variable controls which processor should be targeted for
# generated code.  This controls processor-specific optimizations in
# certain code (currently only OpenSSL) as well as modifying the value
# of CFLAGS to contain the appropriate optimization directive to gcc.
# The automatic setting of CFLAGS may be overridden using the
# NO_CPU_CFLAGS variable below.
# Currently the following CPU types are recognized:
#   Intel x86 architecture:
#       (AMD CPUs)      k7 k6-2 k6 k5
#       (Intel CPUs)    p4 p3 p2 i686 i586/mmx i586 i486 i386
#   Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4
#
# If you experience any problems after setting this flag, please unset
# it again before submitting a bug report or attempting to modify code.
# It may be that certain types of software will become unstable after 
being
# compiled with processor-specific (or higher - see below) optimization 
flags.
# If in doubt, do not set CPUTYPE or CFLAGS to non-default values.
#
#CPUTYPE=i686

is in /etc/defaults/make.conf in 4.x?

-- 
"How fortunate the man with none."
--Dead Can Dance



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050411140326.V75661>