• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: "Future" of llvm-gcc with regards to support
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Future" of llvm-gcc with regards to support


  • Subject: Re: "Future" of llvm-gcc with regards to support
  • From: Salman Khilji <email@hidden>
  • Date: Fri, 24 Feb 2012 15:49:13 -0800

Rumor has it that "people familiar with the matter" said Apple will kill in Xcode 4.4.

llvm-gcc was already a deal breaker for me.  I maintain (or not?) build scripts that allow one to compile Code Sourcery g++ for embedded Linux to natively run on Mac OS X.  Here are the details:

https://github.com/UnhandledException/ARMx/wiki/Sourcery-G++-Lite-for-ARM-GNU-Linux-(2009q3-67)-for-Mac-OS-X

I am assuming that gcc likes to be compiled only with gcc (may be someone has tried clang to compile gcc?, don't know).

The XCode 4.0 (or 4.1?) shipped with a version of llvm-gcc that failed to compile gcc and crashed with an out-of-memory error---yeah, I know, I should have filed a bug report, but I didn't :-(  I had to specifically set my compiler to point to gcc-4.2 to get things to compile correctly.  Now that gcc is gone, and only llvm-gcc and clang are available, I am too scared to even try.

When llvm-gcc is finally gone, it will make it even harder for me to compile a cross toolchain on the Mac.  With llvm-gcc around, I hope to be able to update my scripts someday and publish it for Lion (the current ones are for SL).  With only clang, I _may_ be able to get the toolchain to compile _only_ if I am willing to lose all of my hair over it!

Salman


On Feb 24, 2012, at 11:03 AM, Brad Oliver wrote:

> Hi all,
>
> As part of our migration to Clang, I'm curious what the state of llvm-gcc is in terms of bugfixes and support.
>
> For example, has llvm-gcc seen any love between Xcode 4.0 and Xcode 4.3 or is it basically frozen in time from a few years ago? Doing a llvm-gcc -v, I see this:
>
> Xcode 4.3: LLVM build 2336.1.00
>
> Xcode 4.0.2 under 10.6.8: LLVM build 2335.9
>
> That's not a huge difference. I realize Clang is the One True Way, so my curiosity is mainly about coping with codegen bugs that we've hit in llvm-gcc and planning a way around that.
>
> If the answer is "llvm-gcc will not see fixes and has not since Xcode 4.0; forge ahead with Clang", then that's good enough.
>
> --
> Brad Oliver
> email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: "Future" of llvm-gcc with regards to support
      • From: Jean-Daniel Dupas <email@hidden>
References: 
 >"Future" of llvm-gcc with regards to support (From: Brad Oliver <email@hidden>)

  • Prev by Date: Re: "Future" of llvm-gcc with regards to support
  • Next by Date: Is there any way Xcode can munge up folder names in an application package
  • Previous by thread: Re: "Future" of llvm-gcc with regards to support
  • Next by thread: Re: "Future" of llvm-gcc with regards to support
  • Index(es):
    • Date
    • Thread