Re: Clang as default compiler November 4th

Fwiw, I plan to fix this issue, but even if I didnt. This isnt
a problem in clang rather than in llvm asm. So it can be easily
worked around by CFLAGS+=-no-integrated-as.

Roman

On Tue, Sep 11, 2012 at 11:22:44PM +0200, Patrick Lamaiziere wrote:
> Le Mon, 10 Sep 2012 16:12:07 -0500,
> Brooks Davis <brooks_at_freebsd.org> a ?crit :
> 
> Hello,
> 
> > For the past several years we've been working towards migrating from
> > GCC to Clang/LLVM as our default compiler.  We intend to ship FreeBSD
> > 10.0 with Clang as the default compiler on i386 and amd64 platforms.
> > To this end, we will make WITH_CLANG_IS_CC the default on i386 and
> > amd64 platforms on November 4th.
> 
> Last time I've checked on 9.X [mid August, FreeBSD clang version 3.1
> (branches/release_31 156863) 20120523], Clang still produces invalid
> code (some nopl (%eax)) for the AMD Geode LX (i586 CPU found on some
> ALIX board or Soekris NET5501). I don't know if this is also a concern
> with older CPU (Pentium 2/1) ?
> 
> http://llvm.org/bugs/show_bug.cgi?id=11212
> http://lists.freebsd.org/pipermail/freebsd-current/2011-October/028588.html
> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/168253
> 
> > What does the mean to you?
> 
> Well, I will not be able to run FreeBSD from scratch on my soekris :-)
> 
> Best regards.
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"