Correct CPUTYPE= for Intel Celeron 2.50GHz (2500.10-MHz 686-class CPU)

2006-06-09 Thread Frank Steinborn
Hello,

can someone tell what the right choice for CPUTYPE in /etc/make.conf
is for that CPU?

And, is it safe to build kernel and world with --march= too?

Thanks,
Frank
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Correct CPUTYPE= for Intel Celeron 2.50GHz (2500.10-MHz 686-class CPU)

2006-06-09 Thread John Nielsen
On Friday 09 June 2006 09:20, Frank Steinborn wrote:
 can someone tell what the right choice for CPUTYPE in /etc/make.conf
 is for that CPU?

You probably want:
CPUTYPE?=pentium4

See /usr/share/examples/etc/make.conf for a full list.

 And, is it safe to build kernel and world with --march= too?

It should be safe to build world and kernel with CPUTYPE specified in 
make.conf, but additional compile flags are typically not guaranteed to work.

JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Correct CPUTYPE= for Intel Celeron 2.50GHz (2500.10-MHz 686-class CPU)

2006-06-09 Thread Frank Steinborn
John Nielsen wrote:
 You probably want:
 CPUTYPE?=pentium4

If I put a ? after CPUTYPE, buildworld won't use CPUTYPE, correct? Is
it better to do so, or is it safe to use CPUTYPE=pentium4?

Thanks,
Frank
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Correct CPUTYPE= for Intel Celeron 2.50GHz (2500.10-MHz 686-class CPU)

2006-06-09 Thread John Nielsen
On Friday 09 June 2006 11:48, Frank Steinborn wrote:
 John Nielsen wrote:
  You probably want:
  CPUTYPE?=pentium4

 If I put a ? after CPUTYPE, buildworld won't use CPUTYPE, correct? Is
 it better to do so, or is it safe to use CPUTYPE=pentium4?

Incorrect.  The ? means that if the CPUTYPE is already set (say, from the 
command line), it won't get clobbered by the entry in make.conf. So it's good 
practice to always use ?.  It will get picked up by buildworld either way.

JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Correct CPUTYPE= for Intel Celeron 2.50GHz (2500.10-MHz 686-class CPU)

2006-06-09 Thread Nikolas Britton

On 6/9/06, Frank Steinborn [EMAIL PROTECTED] wrote:

Hello,

can someone tell what the right choice for CPUTYPE in /etc/make.conf
is for that CPU?



CPUTYPE?=pentium2
CFLAGS+= -mtune=prescott
COPTFLAGS+= -mtune=prescott

I find that this produces faster, and safer, code then
-march=pentium4, etc. alone. you can view all the gcc flags here:
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/i386-and-x86_002d64-Options.html


And, is it safe to build kernel and world with --march= too?



With the gcc options I gave to you above yes.



--
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Correct CPUTYPE= for Intel Celeron 2.50GHz (2500.10-MHz 686-class CPU)

2006-06-09 Thread Nikolas Britton

On 6/9/06, Frank Steinborn [EMAIL PROTECTED] wrote:

Hello,

can someone tell what the right choice for CPUTYPE in /etc/make.conf
is for that CPU?



CPUTYPE?=pentium2
CFLAGS+= -mtune=prescott
COPTFLAGS+= -mtune=prescott

I find that this produces faster, and safer, code then
-march=pentium4, etc. alone. you can view all the gcc flags here:
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/i386-and-x86_002d64-Options.html


And, is it safe to build kernel and world with --march= too?



With the gcc options I gave to you above yes.



--
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]