ruby.git/include/ruby/internal/memory.h, branch v3_4_9 The Ruby Programming Language merge revision(s) 61bab1889048f758396acf671c9797d6bc52504b: [Backport #21757] 2026-01-25T07:41:13+00:00 nagachika nagachika@ruby-lang.org 2026-01-25T07:41:13+00:00 28db1b5c3d3a9a5c60762622cb0c3c36c021e8e4 [PATCH] Rename to `struct rbimpl_size_overflow_tag` This struct is used for addition not only for multiplication, so remove the word `mul`, and make the member names more descriptive. 
	[PATCH] Rename to `struct rbimpl_size_overflow_tag`

	This struct is used for addition not only for multiplication, so
	remove the word `mul`, and make the member names more descriptive.
merge revision(s) 99ff0224a564b59df3ba8fbd7911dd41a7fdde34: [Backport #21757] 2026-01-25T07:40:50+00:00 nagachika nagachika@ruby-lang.org 2026-01-25T07:40:50+00:00 c409e343fb14438c2e5304f10ad4c6919e30ac2e [PATCH] Move rbimpl_size_add_overflow from gc.c to memory.h 
	[PATCH] Move rbimpl_size_add_overflow from gc.c to memory.h
Win32: Fix `rbimpl_size_mul_overflow` on arm64 2024-12-17T11:25:06+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2024-11-13T05:45:49+00:00 5a7a1a4a13ae11e4cef274c98e0c5bbcb7b1d192 `_umul128` is specific to x86_64 platform, see higher words by `__umulh` on arm64. 
`_umul128` is specific to x86_64 platform, see higher words by
`__umulh` on arm64.
Allow compilation of C extensions with `-Wconversion` 2024-05-28T05:33:07+00:00 Mike Dalessio mike.dalessio@gmail.com 2024-05-24T17:10:10+00:00 1b8ba1551b26fac906998e34fd2af3f82b433469 C extension maintainers can now compile with this warning option and the Ruby header files will generate no warnings. [Feature #20507] 
C extension maintainers can now compile with this warning option and
the Ruby header files will generate no warnings.

[Feature #20507]
use of stdckdint.h 2024-04-27T12:55:28+00:00 卜部昌平 shyouhei@ruby-lang.org 2024-04-25T07:25:15+00:00 bb5a53820703f5e1af886a0c5ca7178aa976be29 C23 is going to have this header. The industry is already moving towards accepting it; OSes and compilers started to implement theirs. Why not detect its presence and if any, prefer over other ways. See also: - https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2683.pdf - https://reviews.freebsd.org/D41734 - https://reviews.llvm.org/D157331 - https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8441841a1b985d68245954af1ff023db121b0635 
C23 is going to have this header.  The industry is already moving
towards accepting it; OSes and compilers started to implement theirs.

Why not detect its presence and if any, prefer over other ways.

See also:

- https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2683.pdf
- https://reviews.freebsd.org/D41734
- https://reviews.llvm.org/D157331
- https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8441841a1b985d68245954af1ff023db121b0635
Win32: Fix pre-defined macros for platforms 2024-02-11T10:43:06+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2024-02-11T10:43:06+00:00 c77f736bc1e6b73d62e9ba3dcf3dcbeff0657b38 Use `_WIN64` for word-size, `_M_AMD64` for CPU-specific feature. 
Use `_WIN64` for word-size, `_M_AMD64` for CPU-specific feature.
Typo fixes for public headers [ci skip] 2023-12-22T01:34:49+00:00 Alan Wu alanwu@ruby-lang.org 2023-12-22T01:34:49+00:00 0c05551f5812f29c24a30cfbcaa60beab22569d0 






[DOC] Improve documentation to RB_ALLOCV
2022-12-06T05:55:05+00:00

Lars Kanis
lars@greiz-reinsdorf.de

2022-11-01T14:40:52+00:00

81e274c9907c9ddb8fbf8ad0c28cd2b39d6e1639

Although the storage of the opaque Ruby object is an array of VALUEs, the intention of RB_ALLOCV is to allocate bytes of memory.




Although the storage of the opaque Ruby object is an array of VALUEs, the intention of RB_ALLOCV is to allocate bytes of memory.






do not define our own version of memcpy
2022-07-07T13:10:53+00:00

卜部昌平
shyouhei@ruby-lang.org

2022-07-06T00:18:28+00:00

7f64989e5c913ef7624e084badd1a43ce65b3ccc

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]





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]







Revert zero-check for alloca
2021-12-10T09:39:48+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-12-10T09:33:17+00:00

a5baf8d6bc4c21259705f9b4f9aa2d9b9d7ab936

Something weird results in int-in-bool-context and
stringop-overflow warnings.





Something weird results in int-in-bool-context and
stringop-overflow warnings.