Content-Type: multipart/alternative; boundary=20cf303bfb1036c64904a0f47ee0
--20cf303bfb1036c64904a0f47ee0
Content-Type: text/plain; charset=ISO-8859-1
Hi Brandon,
I have investigated this more, and found that SBCL 1.0.46 runs all tests
fine on Windows. The problems you are facing are:
1. Mistakes in BAT file (it corrupts OLISP files by adding SUB symbol at the
end, which triggers that '->' variable error).
2. Make sure that C:/tmp directory exists, by default it doesn't.
3. Pass --dynamic-space-size 1000 in SBCL options, some tests need a lot of
memory.
After fixing the above, I have got the report (attached, added 'txt'
extension for gmail). I haven't fixed the point 1 (I don't know bat
scripting well), but removed that SUB manually.
Fixed OLISP files are attached too.
So, there is nothing wrong with current SBCL and cl-bench on Windows. The
issues I faced earlier are different and do not exist anymore.
Best Regards,
Roman
2011/4/14 Roman Marynchak
> This is a known issue with SBCL for Windows, I faced it myself several
> months ago.
>
> In case somebody wants these (and other Windows issues) to be fixed, the
> first step is to dig a bit and prepare the SBCL-only test case (in other
> words, find the broken SBCL functionality and show why do you think it is
> broken). Report your findings to LP, and wait until somebody is ready to
> work on it. Speaking for myself, I often try to fix SBCL bugs "just for
> fun", as well as other people do, so the probability to get the fix in
> several weeks after the report is high.
>
> Regards,
> Roman
>
--20cf303bfb1036c64904a0f47ee0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi Brandon,

I have investigated this more, and found tha=
t SBCL 1.0.46 runs all tests fine on Windows. The problems you are facing a=
re:

This is a known issue with SBCL for Windows, I faced it myself several mont=
hs ago.

In case somebody wants these (and other Windows =
issues) to be fixed, the first step is to dig a bit and prepare the SBCL-on=
ly test case (in other words, find the broken SBCL functionality and show w=
hy do you think it is broken). Report your findings to LP, and wait until s=
omebody is ready to work on it. Speaking for myself, I often try to fix SBC=
L bugs "just for fun", as well as other people do, so the probabi=
lity to get the fix in several weeks after the report is high.