A Thursday 14 February 2008, escriguéreu: > > In any case, if anybody have access to an Opteron machine and gcc > > 4.2.3, it would be great if he can run the benchmark and contribute > > his feedback. > > Here it is with gcc 4.2.3 on an Opteron 246 (2.0 GHz): > > uller:~$ ./sort423_O2 # with -O2 > Benchmark with 1000000 strings of size 15 > C qsort with C style compare: 0.770000 > C qsort with Python style compare: 0.740000 > NumPy newqsort: 0.630000 > > uller:~$ ./sort423_O3 # with -O3 > Benchmark with 1000000 strings of size 15 > C qsort with C style compare: 0.640000 > C qsort with Python style compare: 0.660000 > NumPy newqsort: 0.400000
And here are my timings with gcc 4.1.3 and using a similar Opteron than yours (270 @ 2.0 GHz): With -O2: Benchmark with 1000000 strings of size 15 C qsort with C style compare: 0.750000 C qsort with Python style compare: 0.700000 NumPy newqsort: 0.690000 With -O3: Benchmark with 1000000 strings of size 15 C qsort with C style compare: 0.670000 C qsort with Python style compare: 0.620000 NumPy newqsort: 0.380000 So, it seems clear that the GCC people has fixed in 4.2.3 the problem with the optimizer introduced in 4.2.1. Very good! By the way, it's nice to see the wide range of platforms that this list allows to test out :-) Cheers, -- >0,0< Francesc Altet http://www.carabos.com/ V V Cárabos Coop. V. Enjoy Data "-" _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
