From what I understand, it's an issue with the gcstub library not building or not being rebuilt.
None of the changes in Martin's patch should affect runtime, they are implementation details. Except he removes the isRunning function from the public API. So it's really an API change that is causing it not to build.
I remember when I added array append caching (and safety to array slice appending), I needed a function which not only allocated memory, it returned the block info. So I added that to druntime's normal GC. But I didn't update the gcstub, and it broke the DLL build. See here:
http://forum.dlang.org/post/4B8352FC.2030408@digitalmars.com
-Steve
From: Walter Bright <walter@digitalmars.com>
To: d-runtime@puremagic.com
Sent: Thursday, March 22, 2012 4:24 PM
Subject: Re: [D-runtime] Arghhh, DLLs broken on Win32 *again*!
What needs to be done to get the current DLL tests to pass?
On 3/22/2012 12:52 PM, Steve Schveighoffer wrote:
http://d.puremagic.com/issues/show_bug.cgi?id=7749
Added a couple days ago.
-Steve
> That may be, but until a better approach is made we
must not break existing code.
Yes, and the best approach is to nail it into the test
suite.
_______________________________________________
D-runtime mailing list
D-runtime@puremagic.com
http://lists.puremagic.com/mailman/listinfo/d-runtime
_______________________________________________
D-runtime mailing list
D-runtime@puremagic.com
http://lists.puremagic.com/mailman/listinfo/d-runtime
_______________________________________________
D-runtime mailing list
D-runtime@puremagic.comhttp://lists.puremagic.com/mailman/listinfo/d-runtime