CPUTYPE and friends, from 'make.conf' benchmark
Chris Rees
utisoft at gmail.com
Tue Dec 6 17:24:11 UTC 2011
On 6 Dec 2011 17:04, <rank1seeker at gmail.com> wrote:
>
> # /bin/sh -c "gcc -v -x c -E -mtune=native /dev/null -o /dev/null 2>&1 |
grep mtune | sed -e 's/.*mtune=//'"
> generic
>
> For target machine, it returned 'generic'
>
> Now only with CPUTYPE in 'make.conf':
> --
> CPUTYPE?=core2
> --
>
> > Also, you should set these in src.conf. Sticking them in make.conf is
> > going to annoy people when you ask why your ports are breaking ;)
> >
> > Chris
>
> I want my ports, to also be optimized for target CPU, not just base.
> None of my ports got broken yet.
I was referring to the other stuff, but CPUTYPE is fine, yes.
> Rebuilded can ...
>
> Tests are started AFTER a reboot!
> There is no bgfsck, as per rc.conf:
> --
> background_fsck=NO
> fsck_y_enable=YES
> fsck_y_flags=-C
> --
>
> Same multiuser enviroment
> Test done once.
>
> After running: '# time unixbench', final score was:
> 395.4
> Completed in 22.8 min
>
> Time is SAME as with generic binaries, but score is just a 1.2 higher,
which is too small to be relevant.
> What do you think about this?
>
I think this is why most people don't bother with setting CPUTYPE ;)
Chris
More information about the freebsd-hackers
mailing list