Regions deallocate the whole "stack" when the region life time is finished.. Who said regons are always dynamic , i would say most would simply allocated sequentually like a nursery and then freed. There is no requirement for free in many cases . . A more complex region may allocate and free but it would need either a gc style heap , a reuse of types ( eg Type(T) available/used list like malloc does ) or ref counting to go about this ( as it would with all rererences that do not have a region life time )
On Sun, Aug 4, 2013 at 1:38 PM, David Jeske <[email protected]> wrote: > On Sat, Aug 3, 2013 at 10:17 PM, Bennie Kloosteman <[email protected]>wrote: > >> ..since regions are just glorified stacks and i presume the stack scan >> code can be used on regions . >> > > I don't follow this.. stacks don't allow dynamic allocation per > stack-frame, while dynamic regions do. > > To me this makes them seem like entirely different beasts. With > call-stacks, allocation and deallocation is mutually bound to the > stack-frame-return. While with dynamic-mutable-regions, we quickly can > witness situations where we would like to reclaim independently of any > statically analyzable motion between stack-frames or blocks. > >
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
