specific query on array de-allocation on the heap

Question

When passing around heap allocated arrays at some point we call:

delete [] ptrName

How does the compiler remember how much memory needs to be de-allocated?

Context:

We've got several programs that throw around pointers to byte arrays on the heap, for various reasons casting between int32, int8 and others as appropriate. When the memory needs de-allocating with a delete call what exactly goes on to make sure the right amount is freed?

Thanks

billz · Accepted Answer · 2013-01-31 11:21:26Z

1

Compiler allocates x bytes of overhead which has the allocated memory information, it knows how much to delete when delete [] is called.

§ 5.3.4 NEW

new T[5] results in a call of operator new, and
new(2,f) T[5] results in a call of operator new.

Here, x and y are non-negative unspecified values representing array allocation overhead; the result of the new-expression will be offset by this amount from the value returned by operator new[]. This overhead may be applied in all array new-expressions, including those referencing the library function operator new[](std::size_t, void*) and other placement allocation

answered Jan 31, 2013 at 11:21

billz

45.6k9 gold badges87 silver badges103 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

ForEveR · Accepted Answer · 2013-01-31 11:07:48Z

0

There is nothing in standard about it. Developers of compiler make decisions, where to store how much memory needs to be deallocated, by writing in some place amount of memory, that will be allocated by new.

answered Jan 31, 2013 at 11:07

ForEveR

56.1k2 gold badges127 silver badges139 bronze badges

Collectives™ on Stack Overflow

specific query on array de-allocation on the heap

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related