This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Some SPECfp results for the simplify-rtx problem



Here're the results of SPECfp2000 on an Athlon 1.2 Ghz MP system
(different machine to last time, you can't compare the numbers) as
asked for by Richard Henderson.

Base is an old GCC version without RTH's simplifiy-rtx.patch and Peak
uses the current GCC CVS that includes the simplifiy-rtx patch set:

Flags are: -O2 -march=athlon -malign-double

                                     Estimated                     Estimated
                   Base      Base      Base      Peak      Peak      Peak
   Benchmarks    Ref Time  Run Time   Ratio    Ref Time  Run Time   Ratio
   168.wupwise       1600     340         471*     1600     336         477*
   171.swim          3100     805         385*     3100     791         392*
   172.mgrid         1800     518         348*     1800     517         348*
   173.applu         2100     685         306*     2100     693         303*
   179.art           2600    1915         136*     2600    1907         136*
   183.equake        1300     336         387*     1300     338         385*
   200.sixtrack      1100     545         202*     1100     522         211*

Fortran 77 tests: 168.wupwise, 171.swim, 172.mgrid, 173.applu,
200.sixtrack, 301.apsi.  
C tests (for reference): 177.mesa, 179.art, 183.equake, 188.ammp

Unfortunatly both compilers have errors and 177.mesa, 188.ammp and
301.apsi fail with an "Output miscompare".

I now run on the same machine tests with GCC with RTH's "address_cost
tweak" installed:

     Base flags: -O2 -march=athlon -malign-double
     Peak flags: -O2 -march=athlon -malign-double -fno-reduce-all-givs
                                     Estimated                     Estimated
                   Base      Base      Base      Peak      Peak      Peak
   Benchmarks    Ref Time  Run Time   Ratio    Ref Time  Run Time   Ratio
   ------------  --------  --------  --------  --------  --------  --------
   168.wupwise       1600     336         477*     1600     339         471*
   171.swim          3100     980         316*     3100     783         396*
   172.mgrid         1800     518         348*     1800     533         338*
   173.applu         2100     694         303*     2100     654         321*
   179.art           2600    1730         150*     2600    1709         152*
   183.equake        1300     339         384*     1300     340         383*
   200.sixtrack      1100     520         211*     1100     491         224*

And the same with the CVS version (without the "address_cost tweak"):

                   Base      Base      Base      Peak      Peak      Peak
   Benchmarks    Ref Time  Run Time   Ratio    Ref Time  Run Time   Ratio
   ------------  --------  --------  --------  --------  --------  --------
   168.wupwise       1600     342         468*     1600     333         480*
   171.swim          3100    1155         268*     3100    1151         269*
   172.mgrid         1800     517         348*     1800     535         336*
   173.applu         2100     693         303*     2100     655         321*
   179.art           2600    1957         133*     2600    1906         136*
   183.equake        1300     333         390*     1300     336         387*
   200.sixtrack      1100     521         211*     1100     501         219*


Btw. Honza just committed a fix for "fcmov" which might fix the
failures I see.

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]