On 5/7/07, Vladimir Makarov <[EMAIL PROTECTED]> wrote:
This is one more df-branch comparison after the last merge branch (done
05/03) with the mainline on the merge point (r124382).
There is a big progress since last my benchmarking on compilation
speed of SPECFP2000 for PPC64. But whatever changed this does not
work well for all platforms and benchmarks. Compilation time for some
platforms even worsened a bit.
The most degradation in code quality were fixed too and even more the
code on the branch is now better for P4.
All toolchains were compiled with --enable-checking=release (-O2 was
used to SPEC2000 benchmarks). Four platforms for benchmarking were
used:
x86_64: 2.6 Ghz Core2.
Itanium: 1.6Ghz Itanium2.
PPC64: 2.5Ghz G5.
Pentium4: 3.2Ghz Pentium4 (additionally -mtune=pentium4 was used).
The attachments contain more verbose info about SPEC2000 results
(there base is df-branch, peak is mainline on the merge point) and can
be used to find what tests still needs attention.
Here is the summary:
Compilation time SPECINT2000 (user time sec):
**********Mainline Branch Change
--------------------------------
x86_64 139.39 148.48 +6.5%
Itanium 446.00 484.56 +8.6%
PPC64 374.33 399.72 +6.8%
Pentium4 253.89 269.43 +4.9%
Note that while I appreciate the benchmarking very much, not
providing details on which SPEC tests regress in compile time is bad.
Can you manually identify the worst offender, ideally by file? Or is it
just overall regressing?
Thanks,
Richard.
