> either "native" or "nocona" (actually native should evaluate to nocona): > > touch _native_test.c && gcc -march=native -### _native_test.c > > should tell which -march and -mtune settings gcc assumes for "native". > > indeed there are some known problems with "native", but i think those are > limited to architectures such as mips and arm. with i386 or amd64 "native" > shouldn't cause any problems. > > i think core2 was always wrong to set in make.conf, because the base gcc > simply > does not support it. however so many people are trying to boost speed etc. by > adding make.conf options they find scattered over the internet and on various > linux dist wikis, that core2 was added as a workaround so people could use it > (even though it wasn't supported).
I still don't understand how bsd.cpu.mk is going to handle "native" as value to set CPUTYPE / MACHINE_CPU, or this is irrelevant? Would it be better to use the following? CPUTYPE?=nocona NO_CPU_CFLAGS=yes NO_CPU_COPTFLAGS=yes CFLAGS+= -march=native Thank you for your clarifications. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
