C++, Free-Store vs Heap
Dynamic allocations with new/delete are said to take place on the free-store,
while malloc/free operations use the heap.
I'd like to know if there is an actual difference, in practice.
Do compilers make a distinction between the two terms? (Free store and Heap, not new/malloc)
See http://www.gotw.ca/gotw/009.htm; it can describe the differences between the heap and the free-store far better than I could:
Free-store:
The free store is one of the two dynamic memory areas, allocated/freed by new/delete. Object lifetime can be less than the time the storage is allocated; that is, free store objects can have memory allocated without being immediately initialized, and can be destroyed without the memory being immediately deallocated. During the period when the storage is allocated but outside the object's lifetime, the storage may be accessed and manipulated through a void* but none of the proto-object's nonstatic members or member functions may be accessed, have their addresses taken, or be otherwise manipulated.
Heap:
The heap is the other dynamic memory area, allocated/freed by malloc/free and their variants. Note that while the default global new and delete might be implemented in terms of malloc and free by a particular compiler, the heap is not the same as free store and memory allocated in one area cannot be safely deallocated in the other. Memory allocated from the heap can be used for objects of class type by placement-new construction and explicit destruction. If so used, the notes about free store object lifetime apply similarly here.
For C++, the difference between the free store and the heap has become purely conceptual. Like a jar for collecting bugs, and one for collecting cookies. One is labeled one way, the other another. This designation is meant to drive home the point that you NEVER mix "new" and "delete" with "malloc", "realloc", or "free" (or bit level sets for that matter).
During interviews it's good to say that "new and delete use the free store, malloc and free use the heap; new and delete call the constructor and destructor, respectively, however malloc and free do not." Yet, you will often hear that the memory segments are really in the same area - however, that CAN be compiler specific, that is to say, it is possible that both can designate different memory spaces as pools (not sure why it would be, though).
Mike Koval's answer covers the theory quite well. In practice, however, they are almost always the same region of memory -- in most cases if you dig into the compiler's implementation of new, you'll find it calls malloc().
In other words: from the machine's point of view, heap and free store are the same thing. The distinction exists inside the compiler.
To make things even more confusing, before the advent of C++ we said "heap" to mean what is now called "free store."
The term "heap" may also refer to a particular data structure, but in the context of the C++ malloc, free, new, and delete operations the terms "heap" and "free store" are used more or less interchangeably.
Heap and free-store aren't supposed to be interoperable. In constrained contextes like in AVR 8-bit micro controllers with c++11 Standard Library, they cannot even be used in the same program. Free store and heap do their allocations in the same memory space, overwriting each other structures and data. In this context, Free store is different and incompatible with Heap because the "new/delete free store library" is simpler (and quicker) than the "Malloc/free/realloc/calloc heap library" and thus provides huge memory usage gains to the C++ embedded programmer (in a context where you have only 512 bytes of RAM).
See 8-bit c++11/14 Standard Library at https://github.com/ambroise-leclerc/ETL/tree/master/libstd