Apple has already switched to clang, that happened with XCode 4. Previously, they shipped both and old version of GCC (4.2), and a compiler which used the GCC frontend and an LLVM backend. They made this switch because they didn't like the GPL version 3, which recent versions of GCC (and other GNU software) use.
There are two different projects for using GCC as a frontend for LLVM, called llvm-gcc and DragonEgg, with the latter being more up-to-date, I believe. There wouldn't be any point in using GCC as a front-end for clang, since clang is just a front-end for LLVM. On Sun, Sep 18, 2011 at 6:28 PM, John Clements <cleme...@brinckerhoff.org> wrote: > FYI: Extracted from an audio mailing list, of possible interest re: Mac > compilation; it looks like Apple's switching to clang. In fact, gcc may > (already? soon?) be a front end for clang. > > John > > Begin forwarded message: > >> From: Kyle Sluder <kyle.slu...@gmail.com> >> Date: September 17, 2011 8:58:27 PM PDT >> To: Paul Davis <p...@linuxaudiosystems.com> >> Cc: "coreaudio-...@lists.apple.com API" <coreaudio-...@lists.apple.com> >> Subject: Re: Commandline Tool Chain? >> > > ... > >> So while you can invoke clang directly (don't use GCC anymore; it's >> unsupported) to produce fully functional Mac OS X binaries ... > > ... > > > > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/dev > -- sam th sa...@ccs.neu.edu _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
