Bug #16774
closed
Don't require sub-word atomics
Added by schwab (Andreas Schwab) over 4 years ago.
Updated over 3 years ago.
Description
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.
Files
- Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN to 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED
- Has duplicate Bug #16800: [riscv64-linux] miniruby: thread_pthread.c:1935: rb_sigwait_fd_put: Assertion `old == th' failed. added
- Status changed from Open to Closed
- Backport changed from 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED to 2.5: REQUIRED, 2.6: REQUIRED, 2.7: DONE
ruby_2_7 ba6f0879448ebc80c7a595c369c59b6d8dfbdf3e merged revision(s) abe2e7de4d1f2d5861d7c9ab9c7e778f2ee1dcd2.
- Backport changed from 2.5: REQUIRED, 2.6: REQUIRED, 2.7: DONE to 2.5: REQUIRED, 2.6: DONE, 2.7: DONE
ruby_2_6 r67932 merged revision(s) abe2e7de4d1f2d5861d7c9ab9c7e778f2ee1dcd2.
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0