Re: Compiling to bytecode

2017-07-16 Thread Alexander Burger
On Sun, Jul 16, 2017 at 10:17:40AM -0400, Matt Wilbur wrote: > The MIPS in this case has 32 registers, 30 of which are general > purpose (though there is some convention, as you might expect). r0 is > hard coded to 0 and r31 is the stack pointer. Sounds good. You need 12 for the 6 VM registers

Re: Compiling to bytecode

2017-07-16 Thread Alexander Burger
On Sun, Jul 16, 2017 at 08:04:53AM -0400, Matt Wilbur wrote: > Reality just intervened - my MIPS processor is native 32-bit. So I think > emu is my only option. :( Well, it would also be possible to generate code for a 32-bit machine, using two physical registers for a single pil64-VM register.

Re: Compiling to bytecode

2017-07-16 Thread Matt Wilbur
On Sun, Jul 16, 2017 at 7:44 AM, Matt Wilbur wrote: > On Sun, Jul 16, 2017 at 7:26 AM, Alexander Burger > wrote: >> On Sat, Jul 15, 2017 at 03:02:02PM -0400, Matt Wilbur wrote: >>> Correct. I am working on a project that uses a MIPS processo embedded

Re: Compiling to bytecode

2017-07-15 Thread George Orais
Hi Matt, Nice plan you got! Maybe I can share you some of my experience implementing PIL64 to FPGA. But got some questions first: 1. Is it a 32bit or a 64bit MIPS? 2. Is it running an OS? I'm not sure but I think someone was attempting to port PicoLisp to an old SGI? And I'm sure that SGI was

Re: Compiling to bytecode

2017-07-15 Thread Matt Wilbur
On Sat, Jul 15, 2017 at 7:21 AM, Jakob Eriksson wrote: > Still, PicoLisp source, I mean the program you write in PicoLisp, > (not the C code) can become quite large depending on your application. > > We mitigated this, not by storing the "compiled" structures of pointers >

Re: Compiling to bytecode

2017-07-15 Thread Matt Wilbur
On Sat, Jul 15, 2017 at 6:56 AM, Alexander Burger wrote: > > Hi Matt, > > > In order to minimize flash footprint, I was wondering if it would be > > possible to compile code down to byte code? The reason i wanted to do that > > is then I could make of some library functions

Re: Compiling to bytecode

2017-07-15 Thread Jakob Eriksson
Still, PicoLisp source, I mean the program you write in PicoLisp, (not the C code) can become quite large depending on your application. We mitigated this, not by storing the "compiled" structures of pointers to pointers. (Although we could have - but that would have been complicated to

Re: Compiling to bytecode

2017-07-15 Thread Alexander Burger
Hi Matt, > In order to minimize flash footprint, I was wondering if it would be > possible to compile code down to byte code? The reason i wanted to do that > is then I could make of some library functions in reader macros off-target > and avoid installing libraries on the target. Can you