The heap is in flux. We did not leave the code from FPOS in a stable state.
HEAP is normally USERMODE memory management of a linked list(stacked chunks of
choclate instead of a stack of papers in order).Hence the C is a bit messy.
HEAP must be initialized when the papging unit(VMM) prepares to flip the paging
bit.From then on, HEAP automagically allocated and frees ram by variable,
paging unit/heap unit work as one to allocate/free by page(4K chunk) as the OS
requires it.
A lot of units here on out require RAM(therfore HEAP) to function. Once this
unit is fixed, we can move on.
I have reworked some of BrokenThorn examples from C at the moment, I am merging
in FPOS code and parts from the FPC RTL.Code is currently UNSTABLE.
Original issue reported on code.google.com by frazzled...@gmail.com on 25 Apr 2011 at 9:18
Original issue reported on code.google.com by
frazzled...@gmail.com
on 25 Apr 2011 at 9:18