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: "Sean McBride" <email@hidden>
- Date: Tue, 8 Sep 2009 12:12:10 -0400
- Organization: Rogue Research Inc.
On 9/7/09 7:47 PM, Markus Spoettl said:
>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.
Clang is very promising, but also very new. So of course there are some
issues. You don't say what you'd be switching _from_ though. In my
experience 1) clang lacks some compiler warnings gcc has 2) clang does
not support C++ 3) clang has some bugs building GC code for 10.5.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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