Re: [boost] portable precise garbage collector for C++

From: Achilleas Margaritis (axilmar_at_[hidden])
Date: 2007-09-18 10:16:46

Achilleas Margaritis wrote:
> Steven Burns wrote:
>> No, __fastcall is not portable, but it's largely irrelevant to the 
>> algorithm.
>> I think the top-1 question will be: how does it handle cycles?
>>
>> Steven
> 
> Cycles are handled as in every other garbage collector, i.e. objects 
> connected cyclically do not remain for ever in memory.
> 
>>
>> "Larry Evans" <cppljevans_at_[hidden]> wrote in message 
>> news:fclt2h$2v4$1_at_sea.gmane.org...
>>> On 09/16/07 16:56, Achilleas Margaritis wrote:
>>>> Dear boost developers,
>>>>
>>>> You can find a new version of my portable precise C++ garbage collector
>>>> in vault/memory.
>>>>
>>> The file:
>>>
>>>   src/cppgc.cpp
>>>
>>> contains:
>>>
>>> void __fastcall _gc_traits::scan(register void *ptr) {
>>>
>>> is __fastcall portable?

I uploaded a new version in the vault which does not have __fastcall. 
But it's noticeably slower without it, so I might introduce a macro in 
the future for those platforms that support it.