Actually, I'd like to revise that to two goals, both of which malloc/free meet...
1) minimize pause in non allocating threads 2) alloc/dealloc overhead (more) proportional to rate and memory overhead, not total heap size Both of these Achilles heels occur in collectors which trace or compact.. Including classic compacting GC and RC+cycle-finding. RC+cycle finding may be able to better minimize these costs than compacting GC, since some reachability can be determined without a trace. * I agree real time allocation is a chimera.. That is not our goal. On Oct 14, 2013 7:45 AM, "david j" <[email protected]> wrote: > > On Oct 14, 2013 7:43 AM, "david j" <[email protected]> wrote: > > At the risk of sounding like a broken record, the problem we are trying > to solve is memory safety without a perviousness world stop. > > "...without a perceived world stop" > > > Malloc/free operations can degenerately take very long amounts of time.. > What they will NOT do is stop other non allocating threads. >
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
