Re: Clang as default compiler November 4th

2012-09-18 Thread Roman Divacky
Fwiw, I commited the "dont use long nops on amd geode" thing into llvm a few minutes ago. So this issue doesnt exist anymore. On Wed, Sep 12, 2012 at 07:19:07PM +0400, Lev Serebryakov wrote: > Hello, Patrick. > You wrote 12 2012 ?., 1:22:44: > > PL> Well, I will not be able to run FreeBS

Re: Clang as default compiler November 4th

2012-09-18 Thread Mehmet Erol Sanliturk
On Tue, Sep 18, 2012 at 7:23 AM, Tijl Coosemans wrote: > On 15-09-2012 17:39, Mehmet Erol Sanliturk wrote: > > On Sat, Sep 15, 2012 at 7:30 AM, Tijl Coosemans > wrote: > >> On 15-09-2012 16:09, Roman Divacky wrote: > >>> Is this correct? > >>> > >>> lev ~$ ./cos 1.23456789e20 > >>> 6.031937e-01

Re: Clang as default compiler November 4th

2012-09-18 Thread Tijl Coosemans
On 15-09-2012 17:39, Mehmet Erol Sanliturk wrote: > On Sat, Sep 15, 2012 at 7:30 AM, Tijl Coosemans wrote: >> On 15-09-2012 16:09, Roman Divacky wrote: >>> Is this correct? >>> >>> lev ~$ ./cos 1.23456789e20 >>> 6.031937e-01 >>> -9.629173e-02 >>> 2.814722e-01 >> >> Yes, that's what the libm call

Re: enabling libc++ by default when building with clang

2012-09-18 Thread David Chisnall
On 17 Sep 2012, at 20:10, Brooks Davis wrote: > One key question is, when do we want to throw this switch? Do we do it > now so people using clang start using it sooner or do we wait until > we've switched the default compiler and things have settled a bit? As dim says, enabling it does not mean