You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
p_memcpy(void*, void*, int, int) needs to be implemented.
There's a lot of implementations of memcpy -- newlib has a fantastically huge one for each platform.
Some notes from the source:
* 0. User space
* 1. Specific to bsb/device/os
* 2. Should be lightning fast
* 3. Add "safety" compile switch for error checking
* 4. Function should not call any
* 5. Need a different call per chip, board, O/S?
and some personal observations:
Of course it's userspace.
Why? How? (If it's specific to a bsp/dev/os, shouldn't it be dev_ops?)
This needs to be clearly defined; newlib variants can be found with fantastical memcpy implementations, optimizing for all sorts of things, and OpenBSD has it in libkern.
How should this be named? Kernel style doesn't dictate those names (as I can tell). I would rather a compile flag along the lines of FAIL_FAST but others would name it __SAFE_MEMCPY.
p_memcpy(void*, void*, int, int)
needs to be implemented.There's a lot of implementations of
memcpy
-- newlib has a fantastically huge one for each platform.Some notes from the source:
and some personal observations:
FAIL_FAST
but others would name it__SAFE_MEMCPY
.Memcpy isn't a terribly special function, but gets a lot of press for being a pusher of bits.
The text was updated successfully, but these errors were encountered: