ruby.git - The Ruby Programming Language

Age	Commit message (Collapse)	Author
2025-08-12	Replace stdatomic ops with explicit mem order	John Hawthorn
	My previous pass missed these atomic operations using operators.
2025-08-12	Implement rbimpl_atomic_value_load	John Hawthorn
	This only adds the rbimpl_ version to include/ruby/atomic.h so that it is not a new public interface. We were already using RUBY_ATOMIC_VALUE_LOAD in a few locations. This will allow us to use other memory orders internally when desired.
2025-08-12	Update rbimpl_atomic_* to all take a memory order	John Hawthorn

2025-08-12	Rename rbimpl_atomic.*_set to _store	John Hawthorn
	"store" is the terminology the C11 standard uses, which allows us to use this as a fallback. This only changes the private rbimpl_ version of the method, RUBY_ATOMIC_SET et al. keep the same name.
2025-07-17	`atomic.h`: Add C11 <stdatomic.h> implementation	fuhsnn
	The implementation is only active if `HAVE_STDATOMIC_H` is defined, and only after the compiler fails to match all currently supported systems.
2025-07-17	`atomic.h`: Use explicit logic for 32-bit #else branches	fuhsnn
	These branches are only active for 32-bit Windows and Solaris platforms, codify the fact by changing `#else` to `#elif`'s that explicitly include those targets and `#error`-out otherwise.
2025-05-14	Reduce `Object#object_id` contention.	Jean Boussier
	If the object isn't shareable and already has a object_id we can access it without a lock. If we need to generate an ID, we may need to lock to find the child shape. We also generate the next `object_id` using atomics. Notes: Merged: https://github.com/ruby/ruby/pull/13298
2025-04-30	get_next_shape_internal: Skip VM lock for single child case	Jean Boussier
	If the shape has only one child, we check it lock-free without compromising thread safety. I haven't computed hard data as to how often that it the case, but we can assume that it's not too rare for shapes to have a single child that is often requested, typically when freezing and object. Notes: Merged: https://github.com/ruby/ruby/pull/13191
2025-04-18	Work on ATOMIC_VALUE_SET	John Hawthorn
	Notes: Merged: https://github.com/ruby/ruby/pull/12921
2024-11-02	Include windows.h for `LONG` and `Interlocked` functions	Nobuyoshi Nakada
	Notes: Merged: https://github.com/ruby/ruby/pull/11985
2024-06-07	Cast `RUBY_ATOMIC_PTR_CAS` arguments	Nobuyoshi Nakada
	As well as `RUBY_ATOMIC_PTR_EXCHANGE` and `RUBY_ATOMIC_PTR_LOAD`.
2024-02-11	Win32: Fix pre-defined macros for platforms	Nobuyoshi Nakada
	Use `_WIN64` for word-size, `_M_AMD64` for CPU-specific feature.
2023-12-10	Add RUBY_ATOMIC_{PTR_,}FETCH macros for atomic loads	KJ Tsanaktsidis
	This can already be emulated by doing an atomic fetch_add of zero, but this is more explicit. [Bug #19994]
2021-09-24	Align the implementation precedences with `rb_atomic_t` definition	Nobuyoshi Nakada
	On MinGW, where both of Win32 API and GCC built-ins are available, the mismatch of implementations to the definition caused lots of warnings.
2021-09-22	include/ruby/atomic.h: rework	卜部昌平
	Reduce macros to do the same things in inline functions instead. This way assertions can be made granular. Notes: Merged: https://github.com/ruby/ruby/pull/4848
2021-09-15	include/ruby/atomic.h: add doxygen	卜部昌平
	Must not be a bad idea to improve documents. [ci skip] Notes: Merged: https://github.com/ruby/ruby/pull/4835
2021-03-07	Removed a typo in a comment [ci skip]	Nobuyoshi Nakada

2020-12-24	Use RBIMPL_COMPILER_{SINCE,BEFORE} for MSVC	Nobuyoshi Nakada
	Pointed out by @shyouhei. NOTE: Already we have dropped the support for older MSVCs, probably prior to 1300 or 1400. Remove the conditional code, especially in win32/Makefile.sub.
2020-12-24	Expose atomic operation macros with RUBY prefix	Nobuyoshi Nakada
	Now we need atomic operations, which are lighter than mutex, more widely for extension libraries because of Ractor. Notes: Merged: https://github.com/ruby/ruby/pull/3983