Date: Sun, 25 Sep 2022 23:38:10 +0200 From: Christian Weisgerber <naddy@mips.inka.de> To: Dimitry Andric <dim@freebsd.org> Cc: Jan Beich <jbeich@freebsd.org>, Christian Weisgerber <naddy@mips.inka.de>, freebsd-current@freebsd.org Subject: Re: Did clang 14 lose some intrinsics support? Message-ID: <YzDKQsfciGd%2BJBQ5@lorvorc.mips.inka.de> In-Reply-To: <1A903FD8-D904-4B91-ABC4-2F704F0E2CF4@FreeBSD.org> References: <YzCL/%2BUEhLy7kHaL@lorvorc.mips.inka.de> <zgen-6zwv-wny@FreeBSD.org> <1A903FD8-D904-4B91-ABC4-2F704F0E2CF4@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Dimitry Andric: > > See https://github.com/llvm/llvm-project/commit/e5147f82e1cb > > > > - Instead of __builtin_ia32_pabsd128 maybe use _mm_abs_epi32 > > - Instead of __builtin_ia32_pabsd256 maybe use _mm256_abs_epi32 > > I'm wondering why this rather fragile method is chosen? If you want to > know whether SSE is supported, you check for __SSE__, and similarly > __SSE2__, __AVX__ and a bunch of others. That is also portable to gcc. __AVX__, for instance, is not defined unless you compile with -mavx, which also allows the compiler to issue AVX instructions during normal code generation. -- Christian "naddy" Weisgerber naddy@mips.inka.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YzDKQsfciGd%2BJBQ5>