Announcement

Collapse
No announcement yet.

Compiler Benchmarks Of GCC, LLVM-GCC, DragonEgg, Clang

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • XorEaxEax
    replied
    Originally posted by nanonyme View Post
    -mtune=native is redundant if you're using -march=native.
    -fomit-frame-pointer breaks debuggability in x86.
    -O3 has bugs and might slow down run-time in many cases.
    -O3 has been stable to compile with for ages, I can't recall having encountered any program that compiles with -O2 which has problems with -O3 in years. Also I haven't encountered any cases where -O3 is slower than -O2 in ages, so obviously these tests should be done with -O3, especially since that's where most of the new optimizations will end up.

    Leave a comment:


  • XorEaxEax
    replied
    Originally posted by Tgui View Post
    Good article, nice graphs and happy bday!

    I'd bet with time that LLVM using compilers will catch up to GCC in the rest of the tests.
    Possibly, but nether compiler is standing still in development so only the future will tell.

    Leave a comment:


  • allquixotic
    replied
    The last sentence of the The John the Ripper test analysis:

    Originally posted by Phoronix
    DragonEgg and Clang both lagged behind in performance miserably compared to GCC.
    I think you meant LLVM-GCC and Clang. Because DragonEgg is basically competitive with the older versions of GCC, only falling marginally behind on the Opteron.

    Leave a comment:


  • Drago
    replied
    I wish, there was and latest intel C++ compiler benchmark alongside these.

    Leave a comment:


  • Shining Arcanine
    replied
    What compiler flags were used to build each package? These benchmarks are out of context without that information.

    Leave a comment:


  • Tgui
    replied
    Good article, nice graphs and happy bday!

    I'd bet with time that LLVM using compilers will catch up to GCC in the rest of the tests.

    Leave a comment:


  • nanonyme
    replied
    -mtune=native is redundant if you're using -march=native.
    -fomit-frame-pointer breaks debuggability in x86.
    -O3 has bugs and might slow down run-time in many cases.

    Leave a comment:


  • ChrisXY
    replied
    I may have missed it but what optimizations were used for these tests (especially for gcc)?

    Code:
    -march=native -mtune=native -fomit-frame-pointer -O3
    More, less?

    Leave a comment:


  • nanonyme
    replied
    Sorry, that was ambiguous. As in, Linux kernel compiling can't be done with llvm.

    Leave a comment:


  • nanonyme
    replied
    Originally posted by jakubo View Post
    quite nice.
    it seems llvm likes c-ray but no chess.
    what id like to see now is a linux kernel (compiled with these different compilers) performance benchmark.
    Last I heard, can't be done with llvm.

    Leave a comment:

Working...
X