So why don't most libc/kernel implementations ship a "memcpy" that would query the number of available bytes from the allocator (for heap objects), from the linker (for globals) and from some compiler-generated info (CFI?)?
-
-
It's related but it's way too slow to use it for memcpy, especially in libc. Most malloc implementations aren't capable of providing a comparable feature. Kernel slab allocators are similar to a hardened malloc like OpenBSD malloc other than how they track free objects in slabs.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.