Re: CPUTYPE=native handling

2011-11-19 Thread Alexander Best
On Tue Nov 8 11, Dimitry Andric wrote: On 2011-11-08 01:25, Alexander Best wrote: i've seen dozens of issues, where people set CPUTYPE=native. although this works in a lot of cases, it doesn't in others. why don't we simply add something like . if ${CPUTYPE} == native . error bla

Re: CPUTYPE=native handling

2011-11-08 Thread Roman Divacky
On Tue, Nov 08, 2011 at 08:55:39AM +0100, Dimitry Andric wrote: On 2011-11-08 01:25, Alexander Best wrote: i've seen dozens of issues, where people set CPUTYPE=native. although this works in a lot of cases, it doesn't in others. why don't we simply add something like . if ${CPUTYPE} ==

Re: CPUTYPE=native handling

2011-11-08 Thread Alexander Best
On Tue Nov 8 11, Roman Divacky wrote: On Tue, Nov 08, 2011 at 08:55:39AM +0100, Dimitry Andric wrote: On 2011-11-08 01:25, Alexander Best wrote: i've seen dozens of issues, where people set CPUTYPE=native. although this works in a lot of cases, it doesn't in others. why don't we simply

Re: CPUTYPE=native handling

2011-11-08 Thread Alexander Best
On Tue Nov 8 11, Roman Divacky wrote: On Tue, Nov 08, 2011 at 09:23:52PM +, Alexander Best wrote: On Tue Nov 8 11, Roman Divacky wrote: clang will use core2 for family=6 and model=15 check llvm/lib/Support/Host.cpp what is the problem? The fact that our gcc from the

Re: CPUTYPE=native handling

2011-11-07 Thread Dimitry Andric
On 2011-11-08 01:25, Alexander Best wrote: i've seen dozens of issues, where people set CPUTYPE=native. although this works in a lot of cases, it doesn't in others. why don't we simply add something like . if ${CPUTYPE} == native . error bla . endif in share/mk/bsd.cpu.mk for now? or