aboutsummaryrefslogtreecommitdiff
path: root/libstdc++-v3/acinclude.m4
diff options
context:
space:
mode:
authorJonathan Wakely <jwakely@redhat.com>2022-02-08 13:41:33 +0000
committerJonathan Wakely <jwakely@redhat.com>2022-02-08 14:15:38 +0000
commit8dbb60b8dfc642a81f1c41fde11767150e8f91a5 (patch)
tree3604e58b5fe004d3fc73fa4fa5aa494eac6c2b63 /libstdc++-v3/acinclude.m4
parent676e987b850a7352ece750a8f3a1ac5dae6b3627 (diff)
downloadgcc-8dbb60b8dfc642a81f1c41fde11767150e8f91a5.zip
gcc-8dbb60b8dfc642a81f1c41fde11767150e8f91a5.tar.gz
gcc-8dbb60b8dfc642a81f1c41fde11767150e8f91a5.tar.bz2
libstdc++: Add comment to acinclude.m4
libstdc++-v3/ChangeLog: * acinclude.m4 (GLIBCXX_ENABLE_LOCK_POLICY): Add comment about checking for CAS on correct word size.
Diffstat (limited to 'libstdc++-v3/acinclude.m4')
-rw-r--r--libstdc++-v3/acinclude.m42
1 files changed, 2 insertions, 0 deletions
diff --git a/libstdc++-v3/acinclude.m4 b/libstdc++-v3/acinclude.m4
index 7cc52f4..f53461c 100644
--- a/libstdc++-v3/acinclude.m4
+++ b/libstdc++-v3/acinclude.m4
@@ -3609,6 +3609,8 @@ AC_DEFUN([GLIBCXX_ENABLE_LOCK_POLICY], [
ac_save_CXXFLAGS="$CXXFLAGS"
dnl Why do we care about 2-byte CAS on targets with 4-byte _Atomic_word?!
+ dnl Why don't we check 8-byte CAS for sparc64, where _Atomic_word is long?!
+ dnl New targets should only check for CAS for the _Atomic_word type.
AC_TRY_COMPILE([
#if ! defined __GCC_HAVE_SYNC_COMPARE_AND_SWAP_2
# error "No 2-byte compare-and-swap"