That could very well be explained by the Linux code being re-compiled for Linux on the GNU C compiler, which -though less sophisticated- does not cripple non-Intel CPUs.
It might not have to mean that it's a virtue of Linux itself.
That could very well be explained by the Linux code being re-compiled for Linux on the GNU C compiler, which -though less sophisticated- does not cripple non-Intel CPUs.
It might not have to mean that it's a virtue of Linux itself.
How many of these brainiac souls out there doing the testing actually understand that using Intel based testing tools is demoralizing the efforts of AMD projects. Just how many?![]()
Challenge me, or correct me, but don't ask me to die quietly.
…Pursuit is always hard, capturing is really not the focus, it’s the hunt ...
A lesson to be learned could be to use only non-Intel compilers when compiling for non-Intel CPUs and to use non-Intel libraries (e.g. Yeppp!) while compiling for those CPUs.
Anyone willing to re-compile a BOINC application -and perhaps even the very BOINC client- for his/her AMD CPU, using a non-Intel compiler and those Yeppp! libraries to test this?
I do predict big gains to be made for FX-8350 CPUs running Windows....
Last edited by Dirk Broer; 11-24-2013 at 10:44 PM.
Intel i3. Currently, it's the only model I've been able to try. Might play with some Amazon cloud servers to try it a bit more.
The linux distributable is downloaded already compiled, probably with Intel Compilers from what I gather. I've only once compiled it myself and that was on a Raspberry Pi.
Can the CPU benchmarks of Pyrosim be helpful to provide aditional comparisons?
From what I gather, the Linux distributable was compiled using GCC -which might explain the difference in performance between Windows and Linux.
But then a rather poor C compiler (MicroSoft's?) must have been used for the Windows version that even Intel suffers...
Last edited by Dirk Broer; 11-24-2013 at 11:59 PM.