Today I decided to take the plunge and make clang the default compiler, ie I set WITH_CLANG=yes WITH_CLANG_IS_CC=yes WITH_CLANG_EXTRAS=yes in src.conf. No problem so far. However I wanted to avoid building base gcc ( the whole collection ). Is WITHOUT_GCC what I'm looking for? On another clang note: Is there a page specifying valid settings for -march, my google-foo is failing me. Ie, I'm looking for the equivalent of http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options After successful install I went on to upgrade some ports. Is there a specif PR to use for ports that fails with clang and does not specify to use gcc ( devel/cdecl and deskutils/calibre so were the culprits so far) Best regards Andreas
On 2012-09-11 (Tuesday) 23:49:24 Andreas Nilsson wrote:> Today I decided to take the plunge and make clang the default compiler, ie > I set > > WITH_CLANG=yes > WITH_CLANG_IS_CC=yes > WITH_CLANG_EXTRAS=yes > > in src.conf. No problem so far. However I wanted to avoid building base gcc > ( the whole collection ). Is WITHOUT_GCC what I'm looking for? >It probably is. However, WITHOUT_GCC is not supported yet.> On another clang note: Is there a page specifying valid settings for > -march, my google-foo is failing me. Ie, I'm looking for the equivalent of > http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.htm > l#i386-and-x86_002d64-Options >Take a look at lines 120 and below of contrib/llvm/lib/Target/X86/X86.td in the FreeBSD source directory for supported march switches.
On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote:> Is there a specif PR to use for ports that fails with clang and does > not specify to use gcc ( > devel/cdecl and deskutils/calibre so were > the culprits so far)There is no specific PR. We have not yet placed the requirement on our ports maintainers to deal with clang. For most of the failures, we are already aware of them, as a result of our periodic runs. So, just filing a PR to say "broken on clang" doesn't really help us all that much. mcl
On Wed, Sep 12, 2012 at 11:54:51AM +0300, Alexander Yerenkow wrote:> How about run automated test on two poudriere setups, one with CLANG set > up, other with USE_GCC=4.2 applied to all ports which marked as broken,We have been running various tests for quite some time.> Is there somewhere list of these clang-failing ports?http://wiki.freebsd.org/PortsAndClang . I have been maintaing and updating this for over a year now. mcl
12.09.2012 00:49, Andreas Nilsson wrote:> On another clang note: Is there a page specifying valid settings for > -march, my google-foo is failing me. Ie, I'm looking for the equivalent of > http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-OptionsI'm using the minimum of: : | gcc -E -v -march=native - : | clang -E -v -march=native - because there are number of ports that still doesn't compile with clang or GCC4.6.> After successful install I went on to upgrade some ports. Is there a specif > PR to use for ports that fails with clang and does not specify to use gcc ( > devel/cdecl and deskutils/calibre so were the culprits so far)It's up to you to fix this ports and submit patches. You can always rollback to using GCC. -- Sphinx of black quartz judge my vow.