Re: Got idle CPU cycles?
From: Uncle Al (UncleAl0_at_hate.spam.net)
Date: 09/12/04
- Next message: Tobias Brox: "Re: Got idle CPU cycles?"
- Previous message: Tobias Brox: "Re: Got idle CPU cycles?"
- In reply to: Tobias Brox: "Re: Got idle CPU cycles?"
- Next in thread: Tobias Brox: "Re: Got idle CPU cycles?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 11 Sep 2004 17:33:53 -0700
Tobias Brox wrote:
>
> Uncle Al <UncleAl0@hate.spam.net> wrote:
> > Getting down to business: C++ source is at
>
> > http://www.mazepath.com/uncleal/source.zip
>
> > CHIBigQk is optimized toward Intel Pentium and Xeon, linchi is
> > optimized toward AMD Athlon and Opteron. You must compile to an 80-bit
> > long_double_precision executable. Microsoft compilers **DO NOT**
> > create 80-bit precision executables; Boreland is OK. The executable
> > *must* be run from within a Windows batch file or a Linux script file.
>
> Hrm. You should probably wrap it with autoconfig if you want support
> in the linux/unix community. It was not trivial to compile it.
>
> First attempt on compiling the intel version (I have an idle computer with
> Athlon processor here as well) didn't go at all, gcc simply refused to
> deal with a file with the extention .CPP. I renamed it to lower case.
>
> It compiled fine with gcc, but the linker didn't find the
> long-precition math libraries. Trying again:
>
> gcc -lm ./chibigqk.cpp
>
> gave
>
> /tmp/ccgZbFHK.o(.text+0x148): In function main':
> : undefined reference to operator new[](unsigned int)'
> /tmp/ccgZbFHK.o(.text+0x27b): In function main':
> : undefined reference to operator delete[](void*)'
> /tmp/ccgZbFHK.o(.eh_frame+0x12): undefined reference to __gxx_personality_v0'
> collect2: ld returned 1 exit status
>
> I'm quite sure this can be solved, but I don't have time for it today.
We have four Xeons, two Athlons, and two Pentium4s currently crunching
away happily. They returned benchmark output accurate to all 18
significant figures in CHI. The Xeons are running locally compiled
code. It even runs in Windows, albeit with a 40% performance hit in
any given hardware compared to Linux.
If you can't do it, don't worry about it
If you have no hardware to volunteer, don't worry about it.
And, please, stop whining. This is about product not process. It is
a finite project and self-contained. We'd love to run in a processor
farm in parallel or as individual independent nodes. We'll happily
settle for what we can get as private boxes. The physical experiment
will be completed by Summer 2005 in Wuhan, China.
Then, we will either be goats or gods. I plan for the laurel wreath.
-- Uncle Al http://www.mazepath.com/uncleal/ (Toxic URL! Unsafe for children and most mammals) http://www.mazepath.com/uncleal/qz.pdf
- Next message: Tobias Brox: "Re: Got idle CPU cycles?"
- Previous message: Tobias Brox: "Re: Got idle CPU cycles?"
- In reply to: Tobias Brox: "Re: Got idle CPU cycles?"
- Next in thread: Tobias Brox: "Re: Got idle CPU cycles?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]