[ruby-core:97800] [Ruby master Bug#16774] Don't require sub-word atomics

[ruby-core:97800] [Ruby master Bug#16774] Don't require sub-word atomics

[schwab]

Issue #16774 has been reported by schwab (Andreas Schwab).

----------------------------------------
Bug #16774: Don't require sub-word atomics
https://bugs.ruby-lang.org/issues/16774

* Author: schwab (Andreas Schwab)
* Status: Open
* Priority: Normal
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
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--------------------------------
0001-Don-t-require-sub-word-atomics.patch (1.41 KB)


-- 
https://bugs.ruby-lang.org/

[ruby-core:97971] [Ruby master Bug#16774] Don't require sub-word atomics

[mame]

Issue #16774 has been updated by mame (Yusuke Endoh).


Great.  Thank you.

----------------------------------------
Bug #16774: Don't require sub-word atomics
https://bugs.ruby-lang.org/issues/16774#change-85201

* Author: schwab (Andreas Schwab)
* Status: Open
* Priority: Normal
* Backport: 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED
----------------------------------------
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--------------------------------
0001-Don-t-require-sub-word-atomics.patch (1.41 KB)


-- 
https://bugs.ruby-lang.org/

[ruby-core:99761] [Ruby master Bug#16774] Don't require sub-word atomics

[merch-redmine]

Issue #16774 has been updated by jeremyevans0 (Jeremy Evans).

Status changed from Open to Closed

This was committed at commit:abe2e7de4d1f2d5861d7c9ab9c7e778f2ee1dcd2

----------------------------------------
Bug #16774: Don't require sub-word atomics
https://bugs.ruby-lang.org/issues/16774#change-87265

* Author: schwab (Andreas Schwab)
* Status: Closed
* Priority: Normal
* Backport: 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED
----------------------------------------
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--------------------------------
0001-Don-t-require-sub-word-atomics.patch (1.41 KB)


-- 
https://bugs.ruby-lang.org/

[ruby-core:102942] [Ruby master Bug#16774] Don't require sub-word atomics

[nagachika00]

Issue #16774 has been updated by nagachika (Tomoyuki Chikanaga).

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.

----------------------------------------
Bug #16774: Don't require sub-word atomics
https://bugs.ruby-lang.org/issues/16774#change-91008

* Author: schwab (Andreas Schwab)
* Status: Closed
* Priority: Normal
* Backport: 2.5: REQUIRED, 2.6: REQUIRED, 2.7: DONE
----------------------------------------
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--------------------------------
0001-Don-t-require-sub-word-atomics.patch (1.41 KB)


-- 
https://bugs.ruby-lang.org/

[ruby-core:103228] [Ruby master Bug#16774] Don't require sub-word atomics

[usa]

Issue #16774 has been updated by usa (Usaku NAKAMURA).

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.

----------------------------------------
Bug #16774: Don't require sub-word atomics
https://bugs.ruby-lang.org/issues/16774#change-91306

* Author: schwab (Andreas Schwab)
* Status: Closed
* Priority: Normal
* Backport: 2.5: REQUIRED, 2.6: DONE, 2.7: DONE
----------------------------------------
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--------------------------------
0001-Don-t-require-sub-word-atomics.patch (1.41 KB)


-- 
https://bugs.ruby-lang.org/