|
|
@ -63,7 +63,7 @@ However because `offset` is marked as a GEP inbounds instruction, this will tell
|
|
|
|
LLVM that ptr is allocated and won't alias other allocated memory. This is fine
|
|
|
|
LLVM that ptr is allocated and won't alias other allocated memory. This is fine
|
|
|
|
for zero-sized types, as they can't alias anything. However if we're using
|
|
|
|
for zero-sized types, as they can't alias anything. However if we're using
|
|
|
|
`heap::EMPTY` as a sentinel for a non-allocation for a *non-zero-sized* type,
|
|
|
|
`heap::EMPTY` as a sentinel for a non-allocation for a *non-zero-sized* type,
|
|
|
|
this can cause undefined behaviour. Alas, we must therefore special case either
|
|
|
|
this can cause Undefined Behaviour. Alas, we must therefore special case either
|
|
|
|
cap or len being 0 to not do the offset.
|
|
|
|
cap or len being 0 to not do the offset.
|
|
|
|
|
|
|
|
|
|
|
|
So this is what we end up with for initialization:
|
|
|
|
So this is what we end up with for initialization:
|
|
|
|