I may have a trick to make things easier!

As a first step to validate the idea this is what I tried - I took the
x86-64.linux.base.s and removed the definition of doDe (this was a random
choice). I added the definition of doDe in another assembly (extra.nasm) in
nasm syntax -

global doDe

extern needSymEX

extern redefineCE


align  16

nop

nop

doDe:

    push r13

    mov r13,rbx

    mov r10,[rbx+0x8]

    mov rbx,[r10]

    mov r10,[r13+0x8]

    mov rdx,[r10+0x8]

    call needSymEX

    call redefineCE

    pop r13

    ret

I was able to generate a working picolisp as follows -

as -o x86-64.linux.base.o x86-64.linux.base.s

nasm -f elf64 extra.nasm

cc -o ../bin/picolisp extra.o x86-64.linux.base.o -Wl,--no-as-needed
-rdynamic -lc -lm -ldl -no-pie


I feel pretty sure that I should be able to translate the .s into nasm
syntax fairly mechanically. I have done similar things before. What I love
about nasm is that there is no ceremony code :)

Once all the transformations are known, we can update asm.l and add a new
arch specific program to generate the nasm code directly.



@Alex - I have a follow up question about POSIX requirement - To bet the
basic REPL up and running the POSIX requirement would be limited to getc
from STDIN right?


Regards,
Kashyap

On Mon, Feb 25, 2019 at 1:07 AM <andr...@itship.ch> wrote:

> >> I have been considering the idea of getting picolisp to run on windows
>
> I think there is no easy way to get the posix-build of picolisp to run
> on windows.
> Even if we manage (as we did before with cygwin etc.), the
> posix-dependent parts like fork() are required for all the nice stuff
> (servers, GUI, pilDB).
>
> I think the only way to bring picolisp really to windows is by
> implementing it in .NET.
> Another picolisp VM implementation, like ersatz (java).
>
> This is an huge task.
> As I understand, Alex has no incentive to it, because with his current
> customers and projects it would not be really a big benefit.
> So maybe someone else would do it. Great opportunity to learn about
> picolisp internals, and Alex surely would help if there are questions.
>
> I would like to have picolisp on windows available, but it's not a
> pressure issue for me.
> At the moment I have no capacity for such a project, maybe in a few
> months.
> It surely would be a very exciting project.
>
> - Andreas
>
>
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Reply via email to