Re:GCC 6.1 Released
by netheril96 on Wednesday April 27, 2016 @09:02PM
(#11585903)
When you write custom memory allocator, you request memory with `malloc` or `mmap` first. The return value of those functions are raw storage, not objects with dynamic type of character array. Neither is the return value of you custom `allocate`. Strict aliasing rule does not apply.
[ Parent
| on HN ]
There are no comments on this comment yet.