Andras, > On Apr 24, 2020, at 5:02, Andras Pahi <pa...@t-online.hu> wrote: > > Hi all, > > I have changed the 32bit pil version written in C to compile in 64bit mode > and to support short numbers encoded in the pointers themselves. > That means that (== 64 64) is T for both the 32bit and the 64bit version.
Well, I tried to build it on macos 10.15 and, as far as I can tell, it works :) I was a bit emotional when I tried so I actually ran pil by using the full path, and OMG it worked !!! :) > It passes the picoLisp test suite and tankf33der’ test suite as well. > The tests should be modified to detect this particular version with > (and *CPU (== 64 64)) because it does not support the constructs of pil64. > > No doubt pil64 still has the performance advantage, running tankf33der’s > Test suite: > > pil64 9m40s > pil, 64bit 14m > pil, 32bit 18m40s > > If anyone is interested the sources can be found at > https://github.com/pahihu/picoLisp Is there any other thing that we'd get from pil64 and that we don't get from that new pil32 ? I'm not sure I understand the implications (which might as well mean that, hey, it should work for my purposes ;) > Happy Lisping! Thank you so much !!! Jean-Christophe Helary ----------------------------------------------- http://mac4translators.blogspot.com @brandelune -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
