In the words of the memcpy(3) man page:
The memcpy() function copies len bytes from buffer src to buffer dst. If
the two buffers may overlap, memmove(3) must be used instead.
There is a suspicion that people have been lax about the restriction
on overlapping buffers. Courtesy of tedu@, below
On Sat, Nov 22, 2014 at 01:27:19PM +, Christian Weisgerber wrote:
> In the words of the memcpy(3) man page:
> The memcpy() function copies len bytes from buffer src to buffer dst. If
> the two buffers may overlap, memmove(3) must be used instead.
>
> There is a suspicion that people have
After the first 12 hours, there have been amazingly few build
failures due to memcpy abort:
emulators/sdlmame m68kmake
emulators/sdlmess m68kmake
lang/gcc/4.8ada
lang/gcc/4.9ada
The respective maintainers already have separate ma
> After the first 12 hours, there have been amazingly few build
> failures due to memcpy abort:
>
> emulators/sdlmame m68kmake
> emulators/sdlmess m68kmake
> lang/gcc/4.8ada
> lang/gcc/4.9ada
>
> The respective maintainers alread
On 2014-11-22, Christian Weisgerber wrote:
> emulators/sdlmame m68kmake
> emulators/sdlmess m68kmake
> lang/gcc/4.8ada
> lang/gcc/4.9ada
+ textproc/p5-SWISH-API swish-e
And that's all.
--
Christian "naddy" Weisgerbe
On 23 November 2014 at 07:14, Christian Weisgerber wrote:
> On 2014-11-22, Christian Weisgerber wrote:
>
>> emulators/sdlmame m68kmake
>> emulators/sdlmess m68kmake
>> lang/gcc/4.8ada
>> lang/gcc/4.9ada
>
> + textproc/p5-SWISH-AP
On Sun, Nov 23, 2014 at 08:59:27AM -0500, Kenneth Westerback wrote:
> On 23 November 2014 at 07:14, Christian Weisgerber wrote:
> > On 2014-11-22, Christian Weisgerber wrote:
> >
> >> emulators/sdlmame m68kmake
> >> emulators/sdlmess m68kmake
> >> lang/gcc/4.8
