On Mon, 15 Jan 2018 18:37:47 +0100 Dimitry Andric <dim_at_FreeBSD.org> wrote: > 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. > > [1] https://bugs.llvm.org/show_bug.cgi?id=34347 It looks to me clang is doing fewer libcalls now and more inlining, which is why the configure tests succeed now. That clang generates cmpxchg8b on i486 has always been the case. The fix for 34347 exposes this more now.Received on Mon Jan 15 2018 - 17:26:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:14 UTC