https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119645
Bug ID: 119645
Summary: GCN, nvptx: libstdc++ 'checking for atomic builtins
[...]... no'
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: ams at gcc dot gnu.org, vries at gcc dot gnu.org
Target Milestone: ---
Target: GCN, nvptx
I noticed that for both GCN, nvptx, libstdc++ configury finds:
checking for atomic builtins for bool... no
checking for atomic builtins for short... no
checking for atomic builtins for int... no
checking for atomic builtins for long long... no
I'd have expected that (at least some of) these should be supported (without
libatomic/libgcc function calls)?
That's 'libstdc++-v3/acinclude.m4:GLIBCXX_ENABLE_ATOMIC_BUILTINS', the "Do asm
tests" variant.
I did a quick manual check for nvptx, for the 'int' code, which compiles
without diagnostic, but then the 'grep __atomic_ conftest.s' runs into an
'__atomic_test_and_set_1' call.
Are we missing to implement some primitives for both GCN and nvptx, or is
something wrong with the 'configure' tests?
