Date: Mon, 22 Dec 2014 21:49:58 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Harry Schmalzbauer <freebsd@omnilan.de> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: CPUTYPEs includig avx are suspicious with clang in stable/10 Message-ID: <18B24CB4-0F39-4A7B-982C-9FAA5CE36749@FreeBSD.org> In-Reply-To: <54944D08.8000202@omnilan.de> References: <54944D08.8000202@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 19 Dec 2014, at 17:06, Harry Schmalzbauer <freebsd@omnilan.de> wrote: > > I'm seeing sporadic problems (core dumps) with binaries compiled with > CPUTYPE=core-i-avx. > They run fine on IvyBridge, but fail on Haswells. > Stripping avx from MACHINE_CPU (by defining CPUTYPE=corei7 instead of > core-i-avx) solved all crashes on the haswell system. Can you provide a concrete test case? E.g. binaries with both optimizations, of which one exhibits the crash? > I have no idea if applications like pkg(8) make use of AVX, I'd bet they > don't do. If you put CPUTYPE?=core-i-avx in /etc/make.conf, and recompile ports with that configuration, they can certainly use AVX, if there are parts in the code that can be vectorized (e.g. certain loops). > So I guess it's something wrong with clang. > Unfortuantely I currently don't have a development installation on any > haswell system to provide some useful backtraces, but perhaps somebody > with compiler knowledge can have a look at this problem? It is hard to say anything without more concrete information. :) -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.26 iEYEARECAAYFAlSYg/0ACgkQsF6jCi4glqMn7gCfS9o/cX7wSz5/YX4Q7azAGHyR tlEAoNfkYkgsQEtsuxEgY75pxM2KlO58 =npG6 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18B24CB4-0F39-4A7B-982C-9FAA5CE36749>