Re: Switching from GCC to Clang, any downsides?
Re: Switching from GCC to Clang, any downsides?
- Subject: Re: Switching from GCC to Clang, any downsides?
- From: Jean-Daniel Dupas <email@hidden>
- Date: Tue, 8 Sep 2009 09:34:21 +0200
Le 8 sept. 2009 à 03:37, Chris Suter a écrit :
Hi Markus,
On Tue, Sep 8, 2009 at 3:47 AM, Markus
Spoettl<email@hidden> wrote:
Reading the Snow Leopard review on Ars Technica, the author writes
that
Clang is now Apple's recommended compiler. So I thought I look it
up in the
documentation, but there's not terribly much on Clang at all. In fact
there's not the slightest hint that this statement is true -
judging from
the docs and release notes alone.
I've since switched to Clang and everything appears to be perfectly
fine.
However, since there's so little in information on this topic there
may be
some caveats involved when switching from GCC. Are there?
I know - and love - the static analyzer and what it can do. I'm
specifically
interested in effects that the compiler switch may have on my
executables.
The only effects I know are I get some better warnings and it's
fast and
produces fast executables. So, are there other effects
(specifically bad
ones, if there are any)?
I'm using Xcode 3.2, developing with deployment target and base SDK
10.5, in
case that is relevant.
I tried switching at some point, but found a bug (which has
subsequently been fixed). That scared me so I'm waiting a while before
I switch for good.
I'd be a lot more confident if Apple could tell us how much of their
released stuff is built with it (not much at the moment, I think).
IIRC, some dev tools are build with it (like Xcode).
_______________________________________________
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