diff options
| author | Urabe, Shyouhei <shyouhei@ruby-lang.org> | 2019-04-26 18:01:24 +0900 |
|---|---|---|
| committer | Urabe, Shyouhei <shyouhei@ruby-lang.org> | 2019-04-29 21:52:44 +0900 |
| commit | e7b18ca6d9b45b7e71694557b9fab8152c62c1ed (patch) | |
| tree | f6005283c9c0d362dd237f08328da47a144009df /mjit.c | |
| parent | a116f04ccabe8ce7d0e7312ef0f55f6a2cdd178e (diff) | |
| download | ruby-e7b18ca6d9b45b7e71694557b9fab8152c62c1ed.tar.gz | |
glibc says memcpy cannot take NULL
At least since 2004, glibc's <string.h> annotates memcpy as
__attribute__((__nonnull__)). On the other hand the argv here,
which is passed from rb_funcallv, may be NULL. Practically this
should never be a serious problem but for maximum safety, let's
avoid passing NULL here.
Diffstat (limited to 'mjit.c')
0 files changed, 0 insertions, 0 deletions