Results 1 to 10 of 17

Thread: Fedora To Remain Monogamist Towards GCC

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,186

    Default Fedora To Remain Monogamist Towards GCC

    Phoronix: Fedora To Remain Monogamist Towards GCC

    While FreeBSD 10 is preparing to fully switch to LLVM's Clang compiler and deprecate GCC, don't expect such a compiler change to happen in the Fedora camp in the foreseeable future. Fedora engineers have issued a statement reaffirming their commitment to GCC and stance on "alternative compilers" within this Red Hat distribution...

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

  2. #2
    Join Date
    Dec 2011
    Posts
    2,122

    Default

    I think LLVM does have future potential.
    But right now, I do think GCC produces better results in the real world.

    I think they should keep on using GCC, while also compiling everything with LLVM to make sure everything compiles cleanly.
    Compiling with more than one compiler makes it better.

  3. #3
    Join Date
    Dec 2008
    Posts
    82

    Default A wise decision

    A wise decision from RH engineers.
    While LLVM has some tractions in the JIT compiler area, it doesn't present any clear advantage for replacing GCC in a standard toolchain.
    hobbyists can still install it if they want to test their code with it anyway.

  4. #4
    Join Date
    Dec 2010
    Posts
    1,193

    Default

    Looks like they accidentally banned OpenJDK/IcedTea in favor of GCC’s Java compiler…

  5. #5
    Join Date
    Dec 2009
    Posts
    76

    Default

    Quote Originally Posted by Awesomeness View Post
    Looks like they accidentally banned OpenJDK/IcedTea in favor of GCC’s Java compiler…
    If you read part of the log it will be clear to you that the statement in favour of GCC is only valid for stand alone toolchain compilers like clang. For JIT purposes llvm is still the way to go, otherwise they also would have to ditch llvmpipe is MESA, which is not what will happen.

  6. #6
    Join Date
    Dec 2010
    Posts
    1,193

    Default

    Quote Originally Posted by Lynxeye View Post
    If you read part of the log it will be clear to you that the statement in favour of GCC is only valid for stand alone toolchain compilers like clang. For JIT purposes llvm is still the way to go, otherwise they also would have to ditch llvmpipe is MESA, which is not what will happen.
    I've read the log and yes, in context it's clear. However, there was a one sentence long policy voted upon which does not have any references to that. (“Packages may only build with an alternative compiler to gcc if upstream does not support gcc”)

    And no LLVMpipe is not used to produce any packages. The policy as it was voted, seems to ban OpenJDK/IcedTea for all uses that GCC’s Java compiler can handle.

Posting Permissions

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