Ive resently gotten access to a dual opteron 246 server on which I now run seti with a boinc client compiled to that cpu.
Now Id like to compile a version on the seti client too but I dont seem to get a valid client (its very small only ~650kb and it takes over 10 hours to complete a WU)

The config I useed is as follows

export MYSQL_CONFIG=true
export CFLAGS="-march=opteron -m64 -O3 -fomit-frame-pointer -funroll-loops -fforce-addr -ftracer"
export CXXFLAGS=$CFLAGS
./configure --disable-server
make

this is the result

-rwxr-xr-x 1 root root 645664 Apr 11 12:15 setiathome-4.7.x86_64-unknown-linux-gnu
-rwxr-xr-x 2 root root 715165 Apr 11 12:15 setiathome-4.7.x86_64-unknown-linux-gnu.debug

do anyone have an idea what Im doing wrong or why the compiled client is so slow ?

---

I also had this problem (See post AMD64 client takes 8 hours) although on a single AMD64 machine. Different flags had no effect.

My only solution so far has been to compile the client on a 32bit system (-march=i686) which links against a set of 32 bit libraries on my amd64 system. This one takes ~2 hours.

I noticed that the libm-2.3.2.so file for amd64 (I use debian linux) is much larger than the 32bit version. I asked the debian-amd64 mailing list about this difference and whether it would have an impact but have not received a reply yet. I may yet be proved this has no relevance.

Have a look at http://boinc.berkeley.edu/download_other.php or http://www.lb.shuttle.de/apastron/boincDown.shtml. There are Opteron optimazed clients for Solaris X86 and Linux.

Lars

---

i believe -march=k8 is supposed to work better than =opteron or =athlon64 or =amd64. i had the same problems with 10hr wu's, but ended up using Ned's 64bit linux client so i never figured out what the problem really was