ruby.git/include/ruby/internal/memory.h, branch v3_3_11 The Ruby Programming Language 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.







Fix stack buffer overflow
2021-12-09T16:04:59+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-08-17T13:01:57+00:00

bcc2bb28b04054106f4a36e8fd69b2af6ecb033a

https://hackerone.com/reports/1306859





https://hackerone.com/reports/1306859







include/ruby/internal/memory.h: add doxygen
2021-09-10T11:00:06+00:00

卜部昌平
shyouhei@ruby-lang.org

2021-01-19T03:55:16+00:00

4397e737c57a0722499669f3c60693d2cdeba609

Must not be a bad idea to improve documents. [ci skip]





Must not be a bad idea to improve documents. [ci skip]







sed -i 's/. They/.  They/'
2021-09-10T11:00:06+00:00

卜部昌平
shyouhei@ruby-lang.org

2021-01-14T06:00:54+00:00

94e5953b484517234ad476b1e179d1bdbcbafbd7

Truly editorial fix for comments.  This works better with Emacs'
set-justification-full function. [ci skip]





Truly editorial fix for comments.  This works better with Emacs'
set-justification-full function. [ci skip]







Get `ruby_nonempty_memcpy` to have C linkage
2021-07-13T13:55:17+00:00

xtkoba
69125751+xtkoba@users.noreply.github.com

2021-04-29T14:26:16+00:00

29f6f79e7396018962eb25c5f5e409f5fe28a73b

Fixes [Bug #17788]




Fixes [Bug #17788]






Fixed dangling imemo_tmpbuf
2021-01-02T03:11:52+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2021-01-02T03:11:52+00:00

f690eb34e28b000627e5f0649dd81a04e252286f

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>





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>







ALLOCA_N: do not use RUBY_ALIGNOF
2020-09-25T02:38:33+00:00

卜部昌平
shyouhei@ruby-lang.org

2020-09-23T04:30:56+00:00

873fb1aa4cab7a14f2b38a05f5888c111ea3bc69

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.





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.