Displaying 2 results from an estimated 2 matches for "l3582".
Did you mean:
3582
2025 Apr 23
1
R should add an API routine for safe use of memcpy(), memset() for use with 0-length SEXP
...8b6298b0bedb39fa8deba5c819df/src/main/memory.c#L3575-L3580
>>> [3] https://github.com/r-devel/r-svn/blob/9e597ca8132e8b6298b0bedb39fa8deba5c819df/src/include/R_ext/RS.h#L62-L63
>>> [4] https://github.com/r-devel/r-svn/blob/9e597ca8132e8b6298b0bedb39fa8deba5c819df/src/main/memory.c#L3582-L3587
>>>
>>> Mike C
>>>
>>> On Wed, Apr 23, 2025 at 8:57?AM Michael Chirico
>>> <michaelchirico4 at gmail.com> wrote:
>>>> From R 4.5.0 [1], all builds of R discourage use of INTEGER() [and
>>>> friends REAL(), ... and *_...
2025 Apr 23
1
R should add an API routine for safe use of memcpy(), memset() for use with 0-length SEXP
>From R 4.5.0 [1], all builds of R discourage use of INTEGER() [and
friends REAL(), ... and *_RO() equivalents] on length-0 SEXP [2].
Before R 4.5.0, this was the behavior under --enable-strict-barrier.
That means the following can segfault under strict builds (e.g.
-fsanitize=alignment and -O0):
SEXP x = PROTECT(Rf_allocVector(INTSXP, 0));
SEXP y = PROTECT(Rf_allocVector(INTSXP, 0));
const