| Age | Commit message (Collapse) | Author |
|
|
|
Although the storage of the opaque Ruby object is an array of VALUEs, the intention of RB_ALLOCV is to allocate bytes of memory.
Notes:
Merged: https://github.com/ruby/ruby/pull/6654
|
|
The (sole) use of memcpy in our public header is now replaced to
directly call ruby_nonempty_memcpy, and the previous definition of
memcpy is now internal-only. [Bug#18893]
Notes:
Merged: https://github.com/ruby/ruby/pull/6098
|
|
Something weird results in int-in-bool-context and
stringop-overflow warnings.
|
|
https://hackerone.com/reports/1306859
Notes:
Merged: https://github.com/ruby/ruby/pull/5239
|
|
Must not be a bad idea to improve documents. [ci skip]
Notes:
Merged: https://github.com/ruby/ruby/pull/4815
|
|
Truly editorial fix for comments. This works better with Emacs'
set-justification-full function. [ci skip]
Notes:
Merged: https://github.com/ruby/ruby/pull/4815
|
|
Fixes [Bug #17788]
Notes:
Merged: https://github.com/ruby/ruby/pull/4429
|
|
The count of rb_alloc_tmp_buffer_with_count is the allocation size
counted in VALUE size but not in the requested element size.
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org>
Co-authored-by: Koichi Sasada <ko1@atdot.net>
|
|
Now that RUBY_ALIGNOF behaves like C11's _Alignof. This is not
necessarily the best stack arrangement. We can just give up using
__builtin_alloca_with_align(), and let alloca choose what is optimal.
Notes:
Merged: https://github.com/ruby/ruby/pull/3570
|
|
|
|
To fix build failures.
Notes:
Merged: https://github.com/ruby/ruby/pull/3079
|
|
Devs do not love "impl".
Notes:
Merged: https://github.com/ruby/ruby/pull/3079
|