Date: Fri, 02 Feb 2018 23:45:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224669] [exp-run] Against projects/clang600-import branch Message-ID: <bug-224669-13-seM0tp02Rd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224669-13@https.bugs.freebsd.org/bugzilla/> References: <bug-224669-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224669 --- Comment #60 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Jan Beich from comment #59) > Dimitry, assuming cluster machines support AVX2 how useful an -exp run wi= th > the following in make.conf would be in terms of uncovering Clang crashes? > Would C++98 workaround get in the way if applied for better coverage? >=20 > CPUTYPE ?=3D native > # XXX bug 112997: Haswell-like > MACHINE_CPU +=3D avx2 avx sse42 sse41 ssse3 sse3 popcnt fma3 > .if ${MACHINE_CPUARCH} =3D=3D i386 > MACHINE_CPU +=3D sse2 sse i686 mmx i586 i486 > .endif >=20 > Reading bug 223300 and bug 225488 I get the impression quite a few of our > users tweak CPUTYPE. Hmm, I'm not really a big fan of the 'native' setting, I'd rather just spec= ify the exact CPU we're targeting instead. So if you want AVX2, I think specif= ying CPUTYPE=3Dcore-avx2 should be enough? --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224669-13-seM0tp02Rd>