Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280

Warning: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ..../vb/legacy/post.php on line 280
Search Results - Phoronix Forums

Search:

Type: Posts; User: hubicka; Keyword(s):

Page 1 of 3 1 2 3

Search: Search took 0.00 seconds.

  1. Replies
    17
    Views
    2,651

    Yes, Clang also uses the plugin path and needs it...

    Yes, Clang also uses the plugin path and needs it to build non-trivial projects (like firefox), similarly to GCC. The plugin needs to be downloaded and put into LLVM tree...
  2. Replies
    17
    Views
    2,651

    Yep, Chromium at my side needs a work around for...

    Yep, Chromium at my side needs a work around for incorrect narrowing conversions. I played with fixing it at Chromium side bug got lost in code generators, so ended up hacking GCC frontend to ignore...
  3. Replies
    17
    Views
    2,651

    Well, as usual, this needs to be analyzed to work...

    Well, as usual, this needs to be analyzed to work out if it is bug in webkit or GCC (which in case of such large beast may not be completely trivial to do). I will check if I get some interesting...
  4. Replies
    17
    Views
    2,651

    Just to the degree of building it, chasing out...

    Just to the degree of building it, chasing out all compiler crashes, and verifying it starts & is smaller in binary size that non-LTO and clang binary. Did not figure out how to benchmark anything...
  5. Replies
    17
    Views
    2,651

    See David's blog on GCC's JIT...

    See David's blog on GCC's JIT http://developerblog.redhat.com/2015/04/07/jit-compilation-using-gcc-5-2/
    and also I got around to write something about the LTO and inter-procedural optimization...
  6. Replies
    18
    Views
    4,047

    Hehe, there is not only conversation, but real...

    Hehe, there is not only conversation, but real work going on. GCC 5.0 contains great deal of changes cleaning up interfaces and adding better APIs. Changes are easier with specific goals in mind. ...
  7. Yes, that nailed it. It is not unrolling, but...

    Yes, that nailed it. It is not unrolling, but predictive commoning that makes difference here. Just checked GCC 5 and that also gets 8 accesses:

    .L8: ...
  8. I do not see any wrong code bugs for...

    I do not see any wrong code bugs for -funroll-loops in GCC 4.9. The unroller is not particularly difficult pass and it does not really changed much recently. It tends to expose some bugs related to...
  9. Scimark can be downloaded here...

    Scimark can be downloaded here http://math.nist.gov/scimark2/

    GCC code (with unrolling) http://pastebin.com/mwMQEbzy

    LLVM code http://pastebin.com/D36mA169
  10. Scimark

    Clang's -O3 now packages limited loop unrolling, while GCC needs -funroll-loops. I tried compiling with -O3 -march=native -funroll-loops --param max-unroll-times=2 and on my Intel(R) Core(TM)...
  11. Search for HSA support in GCC :)

    Search for HSA support in GCC :)
  12. Both GNU LD and Gold works with LTO (GCC or...

    Both GNU LD and Gold works with LTO (GCC or LLVM). GCC 5.0 will have its own ICF at LTO time (it is not 100% replacement of Gold's - it finds different set of equivalences. Some functions are...
  13. I re-run the benchmark suite with clang version...

    I re-run the benchmark suite with clang version 3.6.0 (trunk 219925) (llvm/trunk 219924) and GCC 4.9.1. The following are results normalized to GCC -O3 build sorted by clang's relative performance...
  14. Well, Ruby is not that big to run into LTO...

    Well, Ruby is not that big to run into LTO scalability issues. I work on GCC's implementation of LTO and regularly test on FIrefox and Libreoffice...
  15. Interesting, still it would be nice to see data...

    Interesting, still it would be nice to see data with LTO and FDO.
  16. I compile with gold GCC&LLVM plugins and it works...

    I compile with gold GCC&LLVM plugins and it works pretty well. Compiling rubby with -O3 -flto works out of the box, but I seem to get only 1.5% speedup on the "make benchmark" test with GCC (with...
  17. make benchmark?

    I tried to compare GCC 4.9 built ruby with one built with clang version 3.6.0 (trunk 219925clang version 3.6.0 (trunk 219925) with default options (i.e. binary is built with -O3).
    Ruby comes with...
  18. --enable-checking=release

    From a quick glance on compile time results, was the mainline compiler built with --enable-checking=release? Development snapshots are by default built with more checking enabled that makes them...
  19. Replies
    18
    Views
    5,351

    The problem of x.z.y scheme with GCC is that...

    The problem of x.z.y scheme with GCC is that project has grown up too big for that. There are too many APIs/ABIs that are developed in not synchronized manner. Individual components are getting...
  20. Replies
    30
    Views
    4,838

    It is the default only when linker plugin is...

    It is the default only when linker plugin is available, that is not the case of Michael's test apparently.
Results 1 to 20 of 57
Page 1 of 3 1 2 3