Re: Bug in gec ?

Hi Lothar,

This is an exact / precise collector.

The primary requirement, above all else, is that it be reliable and to
that end I have been including vast [it seems] numbers of assertions
in the C implementation.

It is not yet either compacting or generational. Until I can reliably
demonstrate that marking the stack is a precise process, anything
else is superfluous.

A derivative of the primary requirement is that I must be able to understand
it (!), which will also help once I put it out for others to use in the fairly
near future, subject to it working correctly when integrated with gec.

I want to be able to implement long running daemon programs using gec,
[my variant of it] with multi-threading, and I while I am happy that Boehm et al
works in a single thread system, I am not convinced that it would work the
way I want it to for my planned systems.

Regards,

Howard

On Friday 25 Jul 2008, Lothar Scholz wrote:
> Hello Howard,
> 
> Thursday, July 24, 2008, 11:00:52 PM, you wrote:
> 
> HT> Thanks Eric for the fix as below.
> 
> HT> I am continuing to develop my custom Garbage Collector for gec, with
> HT> four outstanding routines needed before stress testing.
> 
> Is this a conservative or an exact garbage collector.
> Sometimes i dream about a precise concurrent compacting garbage collector.
> 



-- 
Howard Thomson

--
"Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former." -- Albert Einstein 


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/