GC, memory leaks and 32/64 bit

[Rainer Schuetze]

On 13.03.2013 08:03, Druzhinin Alexandr wrote:
> On 13.03.2013 13:35, Rainer Schuetze wrote:
>>
>> If the undefined symbols happen to be related to AssociativeArray, my
>> current workaround is to add "alias Associative!(Key,Value)
>> _workaround;" somewhere to force instantiation for the respective Key
>> and Value types.
>>
>> The precise GC needs some type info for the allocated memory, so I have
>> added a TypeInfo parameter to most calls into the GC. This changes the
>> interface, so the precise cannot be plugged into the current proxy
>> implementation.
>>
>> I'm currently cleaning up the precise GC implementation so it can be
>> switched on with a version when compiling druntime. Here is the current
>> state: https://github.com/rainers/druntime/tree/gcx_precise
>>
> What version of dmd and phobos I should use to link against your
> druntime? Undefined symbols weren't AA, its were core.memory and
> something else, but they I guess were the result of different versions
> phobos and druntime.

There were some recent changes with respect to inout on TypeInfo.next 
that don't work with older compilers, so I guess it will only work with 
a pretty recent version of dmd from github. Regarding phobos, it should 
be built on top of druntime from the branch.