When using gdc, I have severe issues with the garbage collector.  I'm contemplating switching to tango, and if it fixes my GC issues, it'll definitely be worth it.

I assume that this bug relates to my issues.  The more complex my allocation/deallocation gets, the faster the program crashes.
http://d.puremagic.com/issues/show_bug.cgi?id=72

Jason House wrote:
> When using gdc, I have severe issues with the garbage collector.  I'm contemplating switching to tango, and if it fixes my GC issues, it'll definitely be worth it.
> 
> I assume that this bug relates to my issues.  The more complex my allocation/deallocation gets, the faster the program crashes.
> http://d.puremagic.com/issues/show_bug.cgi?id=72

Tango uses a modified version of the Phobos GC, so I'm afraid there's no easy answer to your question.  However, if you can find any bugs in the Tango code I'll be more than happy to fix them.


Sean

I will be happy just to know if, actually, they are confirmed as bugs by  Walter!
Also 1258, marked critical, has status new...

Paolo

Sean Kelly wrote:
> Jason House wrote:
>> When using gdc, I have severe issues with the garbage collector.  I'm contemplating switching to tango, and if it fixes my GC issues, it'll definitely be worth it.
>>
>> I assume that this bug relates to my issues.  The more complex my allocation/deallocation gets, the faster the program crashes.
>> http://d.puremagic.com/issues/show_bug.cgi?id=72
> 
> Tango uses a modified version of the Phobos GC, so I'm afraid there's no easy answer to your question.  However, if you can find any bugs in the Tango code I'll be more than happy to fix them.
> 
> 
> Sean

Paolo Invernizzi wrote:
> I will be happy just to know if, actually, they are confirmed as bugs by  Walter!
> Also 1258, marked critical, has status new...


I wasn't aware of that issue.  Most of my attempts for help with gdc boiled down to "check out dstress".  Issue 1258 does indicate that 1.015 by dmd fixed a GC issue, but I know that gdc 0.23 (the latest) is only at d version 1.007.

Sean Kelly wrote:
> Tango uses a modified version of the Phobos GC, so I'm afraid there's no easy answer to your question.  However, if you can find any bugs in the Tango code I'll be more than happy to fix them.


That, in and of itself, is enough of a reason to switch over (and is one of the reasons I suspected I'd be happier with tango... Walter is very busy).  Which version(s) of gdc does tango actively support?  The latest version, 0.23, only corresponds to D 1.007.  I'm not sure what changed between 1.007 and 1.016+ that may break compatibility.  The 2.0 stuff certainly may...

Jason House wrote:

> Sean Kelly wrote:
>> Tango uses a modified version of the Phobos GC, so I'm afraid there's no easy answer to your question.  However, if you can find any bugs in the Tango code I'll be more than happy to fix them.
> 
> 
> That, in and of itself, is enough of a reason to switch over (and is one of the reasons I suspected I'd be happier with tango... Walter is very busy).  Which version(s) of gdc does tango actively support?  The latest version, 0.23, only corresponds to D 1.007.  I'm not sure what changed between 1.007 and 1.016+ that may break compatibility.  The 2.0 stuff certainly may...

Tango should work fine with GDC 0.23 (you need a patch to have it working with latest SVN of GDC) as long as your machine is x86. I believe Bugzilla 1258 is fixed in Tango, btw.

-- 
Lars Ivar Igesund
blog at http://larsivi.net
DSource, #d.tango & #D: larsivi
Dancing the Tango

Lars Ivar Igesund wrote:
> Jason House wrote:
> 
>> Sean Kelly wrote:
>>> Tango uses a modified version of the Phobos GC, so I'm afraid there's no
>>> easy answer to your question.  However, if you can find any bugs in the
>>> Tango code I'll be more than happy to fix them.
>>
>> That, in and of itself, is enough of a reason to switch over (and is one
>> of the reasons I suspected I'd be happier with tango... Walter is very
>> busy).  Which version(s) of gdc does tango actively support?  The latest
>> version, 0.23, only corresponds to D 1.007.  I'm not sure what changed
>> between 1.007 and 1.016+ that may break compatibility.  The 2.0 stuff
>> certainly may...
> 
> Tango should work fine with GDC 0.23 (you need a patch to have it working
> with latest SVN of GDC) as long as your machine is x86. I believe Bugzilla
> 1258 is fixed in Tango, btw.
> 

x86 is a bad assumption...  What about mac support?  I routinely run my project on 32 bit x86, 64 bit x86, and mac.  The latter two are only supported by gdc and is the big reason why I want to be able to use it.

Jason House wrote:
> 
> Paolo Invernizzi wrote:
>> I will be happy just to know if, actually, they are confirmed as bugs by  Walter!
>> Also 1258, marked critical, has status new...
> 
> 
> I wasn't aware of that issue.  Most of my attempts for help with gdc boiled down to "check out dstress".  Issue 1258 does indicate that 1.015 by dmd fixed a GC issue, but I know that gdc 0.23 (the latest) is only at d version 1.007.

1258 is fixed in Tango.  Unused space is cleared upon allocation unless GC.BlkAttr.NO_SCAN is set.  This seemed the most reasonable balance of performance and safety.


Sean

Jason House wrote:
> Lars Ivar Igesund wrote:
>> Jason House wrote:
>>
>>> Sean Kelly wrote:
>>>> Tango uses a modified version of the Phobos GC, so I'm afraid there's no
>>>> easy answer to your question.  However, if you can find any bugs in the
>>>> Tango code I'll be more than happy to fix them.
>>>
>>> That, in and of itself, is enough of a reason to switch over (and is one
>>> of the reasons I suspected I'd be happier with tango... Walter is very
>>> busy).  Which version(s) of gdc does tango actively support?  The latest
>>> version, 0.23, only corresponds to D 1.007.  I'm not sure what changed
>>> between 1.007 and 1.016+ that may break compatibility.  The 2.0 stuff
>>> certainly may...
>>
>> Tango should work fine with GDC 0.23 (you need a patch to have it working
>> with latest SVN of GDC) as long as your machine is x86. I believe Bugzilla
>> 1258 is fixed in Tango, btw.
> 
> x86 is a bad assumption...  What about mac support?  I routinely run my project on 32 bit x86, 64 bit x86, and mac.  The latter two are only supported by gdc and is the big reason why I want to be able to use it.

Tango pretty much runs on mac, as far as I know.  The greatest obstacle there has been a lack of mac users needed for thorough testing. Kashia's help has been invaluable however, and Carlos has been extremely good about reporting mac bugs as well.  So please give it a try, and if you find any problems, let us know :-)


Sean

Jason House wrote:

> Lars Ivar Igesund wrote:
>> Jason House wrote:
>> 
>>> Sean Kelly wrote:
>>>> Tango uses a modified version of the Phobos GC, so I'm afraid there's
>>>> no
>>>> easy answer to your question.  However, if you can find any bugs in the
>>>> Tango code I'll be more than happy to fix them.
>>>
>>> That, in and of itself, is enough of a reason to switch over (and is one of the reasons I suspected I'd be happier with tango... Walter is very busy).  Which version(s) of gdc does tango actively support?  The latest version, 0.23, only corresponds to D 1.007.  I'm not sure what changed between 1.007 and 1.016+ that may break compatibility.  The 2.0 stuff certainly may...
>> 
>> Tango should work fine with GDC 0.23 (you need a patch to have it working with latest SVN of GDC) as long as your machine is x86. I believe Bugzilla 1258 is fixed in Tango, btw.
>> 
> 
> x86 is a bad assumption...  What about mac support?  I routinely run my project on 32 bit x86, 64 bit x86, and mac.  The latter two are only supported by gdc and is the big reason why I want to be able to use it.

GDC 0.23 have several bugs for non-x86 in particular, that affects Tango, it
is not a lack of effort or wanting from our side that is the main
problem :)

-- 
Lars Ivar Igesund
blog at http://larsivi.net
DSource, #d.tango & #D: larsivi
Dancing the Tango