RE: clang tautology

2012-05-29 Thread Dewayne Geraghty
My apologies, I clearly didn't copy the url from the right buffer, Mark Linimon's Ports & Clang wiki is at http://wiki.freebsd.org/PortsAndClang Dewayne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable

Re: clang tautology

2012-05-29 Thread Randy Bush
> Mark Linimon is monitoring the status of ports and clang at > http://blog.vx.sk/archives/25-FreeBSD-Compiler-Benchmark-gcc-base-vs-gcc-ports-vs-clang.html > Which might save you some work. looks like benchmarks, not status of compilability/runability randy _

RE: clang tautology

2012-05-29 Thread Dewayne Geraghty
> -Original Message- > From: owner-freebsd-sta...@freebsd.org > [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Matthew Seaman > Sent: Tuesday, 29 May 2012 5:33 PM > To: Randy Bush > Cc: FreeBSD Stable > Subject: Re: clang tautology > > On 29/05/2

Re: clang tautology

2012-05-29 Thread Randy Bush
>> is the clang build for releng_9 for amd64 in good enough shape that i >> can simply >> csup >> hack make.conf >> make buildworld >> make kernel >> boot single >> make installworld >> mergemaster -cviFU >> reboot this did work. i am now doing a portupgrade to see if i can break

Re: clang tautology

2012-05-29 Thread Matthew Seaman
On 29/05/2012 04:47, Randy Bush wrote: > is the clang build for releng_9 for amd64 in good enough shape that i > can simply > csup > hack make.conf > make buildworld > make kernel > boot single > make installworld > mergemaster -cviFU > reboot > > as if life was normal? Pace Doug'

RE: clang tautology

2012-05-29 Thread Dewayne Geraghty
Good point Doug, I guess the choice between a clang 3.1 and gcc 4.2.1 world/kernel is pending a performance profile comparison. The performance comparison using specific applications (ports) indicates some improvement of gcc 4.6 over 4.2 and certainly gains when openMP is advantageous. Regards,

Re: clang tautology

2012-05-28 Thread Dimitry Andric
On 2012-05-29 04:49, Randy Bush wrote:> trying a clang buildworld and get a bunch of > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/i386.md:4249:29: > warning: self-comparison always evaluates to false [-Wtautological-compare] > && (TARGET_64BIT || DImode != DIm

Re: clang tautology

2012-05-28 Thread Doug Barton
On 5/28/2012 8:47 PM, Randy Bush wrote: > and if i try to follow http://wiki.freebsd.org/BuildingFreeBSDWithClang > i do not see where the clang world and kernel are actually made the > normal bootable. > > is the clang build for releng_9 for amd64 in good enough shape that i > can simply > csup

Re: clang tautology

2012-05-28 Thread Randy Bush
and if i try to follow http://wiki.freebsd.org/BuildingFreeBSDWithClang i do not see where the clang world and kernel are actually made the normal bootable. is the clang build for releng_9 for amd64 in good enough shape that i can simply csup hack make.conf make buildworld make kernel bo

Re: clang tautology

2012-05-28 Thread Randy Bush
and, for a bonus, clang buildworld ... /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/i386.md:196:14: note: use '=' to turn this equality comparison into an assignment (ix86_tune)) == ( ^~ = randy ___ fre

Re: clang tautology

2012-05-28 Thread Randy Bush
> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/i386.md:4249:29: > warning: self-comparison always evaluates to false [-Wtautological-compare] > && (TARGET_64BIT || DImode != DImode)) >^ > 12 warnings generated. apologies. releng

clang tautology

2012-05-28 Thread Randy Bush
trying a clang buildworld and get a bunch of /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/i386.md:4249:29: warning: self-comparison always evaluates to false [-Wtautological-compare] && (TARGET_64BIT || DImode != DImode)) ^ 12 war