Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: Benchmarking GCC 4.2 Through GCC 4.8 On AMD & Intel Hardware

  1. #1
    Join Date
    Jan 2007
    Posts
    14,546

    Default Benchmarking GCC 4.2 Through GCC 4.8 On AMD & Intel Hardware

    Phoronix: Benchmarking GCC 4.2 Through GCC 4.8 On AMD & Intel Hardware

    Here are benchmarks of all major GNU Compiler Collection releases from GCC 4.2.4 through the latest GCC 4.8 development build. Benchmarking was of the seven GCC compiler releases from an Intel Core i7 "Clarksfield" system and an AMD Opteron "Shanghai" workstation.

    http://www.phoronix.com/vr.php?view=17642

  2. #2
    Join Date
    Apr 2010
    Posts
    1,946

    Default

    I wonder if GCC hackers actually use PTS for regression testing? While its easy to benchmark and compare side-by-side, personally I have quite a trouble navigating via webinterface.. :/
    And huge thanks for the article!!

  3. #3
    Join Date
    Nov 2011
    Posts
    65

    Default

    outdated hardware running at vastly different clock speeds and core counts being compared. This is the most uninformative article from Phoronix in a long time.. can we please compare a Bulldozer Opteron versus Intel's latest and have them run at similar clock speeds with the same number of hardware threads ("cores" for AMD and "threads" for Intel via hyperthreading)? or a Bulldozer Opteron versus an equally priced Intel? either way.

    I know the AMD would probably get stomped, but that would be useful information, and it excited me to see that information so I came here to read it and got disappointed.

  4. #4

    Default

    coder543, you seem to have missed the point of the article. It is comparing versions of GCC, not Intel vs. AMD.

  5. #5
    Join Date
    Dec 2009
    Posts
    492

    Default

    A couple of interesting things I see:
    1. In C-Ray, intel was faster with gcc 4.2, amd ends up faster with gcc 4.7/4.8.
    2. In FLAC audio encoding, the stiuation is actually reversed (though the differences are smaller this time): amd start out on top end ends up at the bottom.

  6. #6
    Join Date
    Nov 2011
    Posts
    65

    Default

    Quote Originally Posted by kiwi_kid_aka_bod View Post
    coder543, you seem to have missed the point of the article. It is comparing versions of GCC, not Intel vs. AMD.
    the newer architectures have hugely different personalities and would respond to the different versions of GCC in completely unique ways that these don't.

  7. #7
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,034

    Default

    That doesn't invalidate these results in any way?

  8. #8
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,788

    Default

    Quote Originally Posted by coder543 View Post
    outdated hardware running at vastly different clock speeds and core counts being compared.
    They are not being compared. Only GCC versions are being compared. Perhaps you missed that each image has two groups of comparisons, one for the Intel system, one for the AMD system.

    It's done in the correct way, so that you can compare the performance of the generated code relative to the machine. You are not supposed to compare the Intel results to the AMD results.

  9. #9

    Default

    Michael,

    What GCC flags did you use during testing?

  10. #10
    Join Date
    Nov 2008
    Location
    Madison, WI, USA
    Posts
    862

    Default

    Quote Originally Posted by birdie View Post
    Michael,

    What GCC flags did you use during testing?
    The compiler flags are underneath each graph. If any specific flags were used (e.g. -O3), they are listed beneath the graph for the individual test. The flags that each compiler was built with are at the bottom of the system specs table.

    I'm guessing that for each of these tests, the flags are the default that are used in the individual PTS test profiles.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •