Results 1 to 6 of 6

Thread: GCC 4.4.0 Release Candidate Is Now Out There

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

    Default GCC 4.4.0 Release Candidate Is Now Out There

    Phoronix: GCC 4.4.0 Release Candidate Is Now Out There

    If you are into compilers and have not already tried out the latest bits from GCC 4.4, you may want to give the GCC 4.4.0 Release Candidate 1 a whirl. GCC 4.4.0 RC1 was tar'ed up yesterday and is now ready for testing. GCC 4.4 has a number of benefits over GCC 4.3 in all areas...

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

  2. #2
    Join Date
    Sep 2008
    Posts
    24

    Default

    You must be kidding. The gcc 4.4.0 branch has still 78 "serious" regressions open. (+other bugs, +P4/P5 regressions and other bugs)

  3. #3
    Join Date
    Nov 2007
    Location
    Die trolls, die!
    Posts
    525

    Default

    So will this fix the performance problems that Firefox has been having on Linux if you use GCC 4.4.0 to compile Firefox ??

  4. #4

    Default

    benchmark time. there could be some pretty big speedups if that auto parallelizing kicks in.

    this is the last regression report i can see on the gcc mailing list before the 4.3.0 release
    http://thread.gmane.org/gmane.comp.gcc.devel/96916

    Their release criteria are no P1 bugs and less than 100 P2, see
    http://thread.gmane.org/gmane.comp.gcc.devel/105312 . they passed that months ago, but have been held up by the licensing issues. basically they don't think any of the remain issues are important enough to hold up the release.

  5. #5
    Join Date
    Jul 2008
    Posts
    28

    Default

    Quote Originally Posted by bugmenot View Post
    So will this fix the performance problems that Firefox has been having on Linux if you use GCC 4.4.0 to compile Firefox ??
    no.


    AHHH, FINALLY! GCC 4.4!
    i've been waiting for it for months. finally, some proper c++0x support, although not complete. god, i'm SO gonna use strongly typed enums.

  6. #6
    Join Date
    Sep 2008
    Posts
    24

    Default

    Quote Originally Posted by ssam View Post
    Their release criteria are no P1 bugs and less than 100 P2,
    This policy really should be thought over. There are open P2 regressions that appeared in 3.x and since then have been postponed again and again with each release.

Posting Permissions

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