Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Apr 2012 08:21:57 +1000
From:      Da Rock <freebsd-questions@herveybayaustralia.com.au>
To:        freebsd-questions@freebsd.org
Subject:   Re: using clang
Message-ID:  <4F78D505.5020905@herveybayaustralia.com.au>
In-Reply-To: <20120401130201.272897fc@cox.net>
References:  <4F76DD24.4060104@herveybayaustralia.com.au> <20120331135624.GA46283@ozzmosis.com> <20343.7837.796535.407848@jerusalem.litteratus.org> <20120401073525.1c05bc0f@cox.net> <20344.21184.853321.579064@jerusalem.litteratus.org> <20120401130201.272897fc@cox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 04/02/12 04:02, Conrad J. Sabatier wrote:
> On Sun, 1 Apr 2012 09:06:08 -0400
> Robert Huff<roberthuff@rcn.com>  wrote:
>
>> Conrad J. Sabatier writes:
>>
>>>   Note, too, that none of these exceptions have anything to do with
>>>   my /usr/src builds.  I've been using clang for buildworld and
>>>   buildkernel for quite some time now.
>> 	I've heard that, but I think I'll wait until it becomes the
>> official default.  :-)
> I can well understand your hesitation.  I didn't jump on the clang
> bandwagon for a good while myself, either.
>
> But, from examining and comparing clang's assembly language output
> against gcc's, it does seem pretty apparent that clang produces
> some pretty darned efficient code, frequently using notably fewer
> machine instructions than gcc, so I try to use it now as much as
> possible.  I also find its error and warning messages to be much more
> precise and informative than gcc's, which is a real boon if you do any
> coding yourself.
Tell me about it. I just found the real reason why libreoffice is 
failing when it gets to tests... :)
>
> There's that, plus the fact that the base system's version of gcc (4.2)
> doesn't fully support my processor family type (amdfam10), whereas
> clang does (although, to be fair, gcc 4.6+ does as well).
>
>>>   Hope this helps somewhat.  :-)
>> 	Very much.
>> 	Thank you.
> You'll come around eventually, no doubt.  :-)
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F78D505.5020905>