Re: [Sbcl-devel] Windows SBCL annoyances

[David L. <da...@li...>]

Quoting Far? (fa...@gm...):
> Indeed, your branch fixes this particular problem. Thanks a lot!
> 
> How is the merge going along?

Anton is doing an excellent job of merging changes from upstream into
his tree.  I would recommend use of his tree (or even binaries) over
upstream SBCL to any Windows SBCL user.

Of course, those changes should absolutely end up in upstream SBCL
eventually, too.

But any delay in Windows merging is solely my fault, not Anton's.

> Maybe instead of trying to acheive a complete merge in N perfectly
> separated patches, you could try do one patch at once, get it merged,
> then work on the next patch?

Indeed, I not aiming for a complete patchset in one go.
The order will be roughly:
  - Safepoints (Status: Patch is done, just not pushed yet)
  - I/O refactoring (Status: not yet written at all, but internals will
    be based on existing code).  This is needed so that threading can
    just fall into place afterwards.
  - Threading (Status: Stand-alone patch partly done)
  - AMD 64 support (Status: Patch review not started except for minor
    backend stuff)


d.