Why does OOo hardcode -mtune=pentiumpro?

Nikolas Britton nikolas.britton at gmail.com
Tue Jun 13 09:59:03 UTC 2006


gmake[1]: Entering directory
`/usr/ports/editors/openoffice.org-2.0/work/OOC680_m5/icu/unxfbsdi.pro/misc/build/icu/source/common'
gcc-ooo  -I. -I.  -DHAVE_CONFIG_H -DU_COMMON_IMPLEMENTATION -O
-mtune=pentiumpro  -c -DPIC  -fPIC  -o putil.ao putil.c
putil.c:153: warning: integer constant is too large for "long" type
putil.c:154: warning: integer constant is too large for "long" type
/usr/bin/ar rv libicuuc.a putil.ao
/usr/bin/ar: creating libicuuc.a
a - putil.ao
g++-ooo  -I. -I.  -DHAVE_CONFIG_H -DU_COMMON_IMPLEMENTATION -O
-mtune=pentiumpro  -c -DPIC  -fPIC  -o uobject.ao uobject.cpp
/usr/bin/ar rv libicuuc.a uobject.ao
a - uobject.ao
gcc-ooo  -I. -I.  -DHAVE_CONFIG_H -DU_COMMON_IMPLEMENTATION -O
-mtune=pentiumpro  -c -DPIC  -fPIC  -o locmap.ao locmap.c
/usr/bin/ar rv libicuuc.a locmap.ao
a - locmap.ao

OOo seems to have -mtune=pentiumpro hard coded in, at least for icu.

IIRC -mtune=cputype takes the same args as -march=cputype, why not
translate CPUTYPE=cputype from make.conf into -mtune=cputype...

Or just lead with two, three, options:
If build detects any athlon based chip set -mtune=athlon64.
if build detects any pentiumpro based chip set -mtune=pentium4.
if build detects anything else don't set -mtune.

I really don't like running intel tuned software on my athlon64.


-- 
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/


More information about the freebsd-openoffice mailing list