1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Don't require sub-word atomics

Browse Source 
On some architectures (like RISC-V) sub-word atomics are only available
when linking against -latomic, but the configure script doesn't do that,
causing the atomic checks to fail and the resulting ruby binary is
non-functional.  Ruby does not use sub-word atomic operations, rb_atomic_t
is defined to unsigned int, so use unsigned int when checking for atomic
operations.
This commit is contained in:
Andreas Schwab 2020-04-10 15:34:52 +02:00 committed by Nobuyoshi Nakada
parent 6f28ebd585
commit abe2e7de4d
Notes: git 2020-04-11 11:20:13 +09:00 
Merged: https://github.com/ruby/ruby/pull/3016
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
configure.ac
View File

@ -1498,7 +1498,7 @@ AS_IF([test "$GCC" = yes], [
]) ])
AC_CACHE_CHECK([for __atomic builtins], [rb_cv_gcc_atomic_builtins], [ AC_CACHE_CHECK([for __atomic builtins], [rb_cv_gcc_atomic_builtins], [
AC_TRY_LINK([unsigned char atomic_var;], AC_TRY_LINK([unsigned int atomic_var;],
[ [
__atomic_exchange_n(&atomic_var, 0, __ATOMIC_SEQ_CST); __atomic_exchange_n(&atomic_var, 0, __ATOMIC_SEQ_CST);
__atomic_exchange_n(&atomic_var, 1, __ATOMIC_SEQ_CST); __atomic_exchange_n(&atomic_var, 1, __ATOMIC_SEQ_CST);
@ -1513,7 +1513,7 @@ AS_IF([test "$GCC" = yes], [
]) ])
AC_CACHE_CHECK([for __sync builtins], [rb_cv_gcc_sync_builtins], [ AC_CACHE_CHECK([for __sync builtins], [rb_cv_gcc_sync_builtins], [
AC_TRY_LINK([unsigned char atomic_var;], AC_TRY_LINK([unsigned int atomic_var;],
[ [
__sync_lock_test_and_set(&atomic_var, 0); __sync_lock_test_and_set(&atomic_var, 0);
__sync_lock_test_and_set(&atomic_var, 1); __sync_lock_test_and_set(&atomic_var, 1);