gcc compiler cputype, prescott or nocona confusion

Hi,

When recompiling the world or kernel in FreeBSD i386 Rel 6.1 with,

"# make buildworld"
or
"# make buildkernel KERNCONF=MYSMPCONF"

(or building anything anything else for that matter), even though I have
"CPUTYPE?=nocona" set in my "/etc/make.conf" file the compiler seems to head
back to a default of "-march=prescott" when compiling many of the functions
on a Dual Xeon 3.6g (nocona) machine!

This doesn't happen when compiling for other machine types, I've tried it on a
Dual PentiumPro, Dual PII, Dual PIII setting the CPUTYPE to the correct cpu
type and the -march sticks to the assigned cpu type through all operations
and produces nice quick optimized code.

Why is this so?

Is it because the "nocona" machine type optimization refers to the EMT64
technology and thus is rejected when compiling for i386 targets rather than
amd64 or emt64 targets and Gcc rejects it?

Regards
Scott K
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: gcc compiler cputype, prescott or nocona confusion
    ... This doesn't happen when compiling for other machine types, ... type and the -march sticks to the assigned cpu type through all operations ... Is it because the "nocona" machine type optimization refers to the EMT64 ... amd64 or emt64 targets and Gcc rejects it? ...
    (freebsd-questions)
  • Re: gcc compiler cputype, prescott or nocona confusion
    ... > When recompiling the world or kernel in FreeBSD i386 Rel 6.1 with, ... > This doesn't happen when compiling for other machine types, ... > Is it because the "nocona" machine type optimization refers to the EMT64 ... > amd64 or emt64 targets and Gcc rejects it? ...
    (freebsd-questions)