atomic in i386 Current after CLANG 6 upgrade
Dimitry Andric
dim at FreeBSD.org
Mon Jan 15 17:37:50 UTC 2018
On 15 Jan 2018, at 11:43, Luca Pizzamiglio <pizzamig at freebsd.org> wrote:
>
> I've already received a couple of messages from pkg-fallout about build
> failure on head-i386-default [1] [2] both pointing to the same errors,
> about missing intrinsic symbols related to __atomic_*
>
> The clang documentation about C11 atomic builtins [3] stats that __atomic_*
> are GCC extension and Clang provides them.
>
> It seems to me that this specific GCC-compatible builtin are enabled on
> amd64, but not on i386.
> Is there a way to enable GCC compatible __atomic_ builtin also on i386?
> Or should I provide patches to adopt _c11_atomic_* instead of __atomic_*
> for every ports that need it ?
There is some strangeness going on with an upstream bug fix [1], which
has the unintended side effect of sometimes emitting libcalls to
__atomic functions that we do not have on i386. I've commented on the
upstream bug report, but I do not know an easy workaround at this
point.
-Dimitry
[1] https://bugs.llvm.org/show_bug.cgi?id=34347
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20180115/551d380c/attachment.sig>
More information about the freebsd-current
mailing list