If you want to compile your .pbc to $(EXE) but you don't want
blib/lib/libparrot.a included in each one, you can do it by linking the
generated .o with blib/lib/libparrot.so (you can try "make exec_so
EXEC=" but I'm unsure if it will work correctly)
In order to have this working you must recom
Now EXEC works for ARM (linux) too.
Now Exec works exactly like the jit, I have checked in the missing restart,
fixed some bugs at Parrot_jit_store_retval and make exec_start call runops
instead of calling run_compiled directly, so now all test are successful.
Have fun.
Daniel.
On Fri, Aug 08, 2003 at 01:48:17PM -0300, Daniel Grunblatt wrote:
> Now Exec works exactly like the jit, I have checked in the missing restart,
> fixed some bugs at Parrot_jit_store_retval and make exec_start call runops
> instead of calling run_compiled directly, so now all test are successful.
On Friday 08 August 2003 14:16, Nicholas Clark wrote:
> On Fri, Aug 08, 2003 at 01:48:17PM -0300, Daniel Grunblatt wrote:
> > Now Exec works exactly like the jit, I have checked in the missing
> > restart, fixed some bugs at Parrot_jit_store_retval and make exec_start
> > call runops instead of cal
I have checked in a patch to make the following work:
./parrot -o life.o examples/assembly/life.pbc
So, don't use test_main anymore.
I made this storing the pointer to the -o argument in the interpreter string
register 0 to make it visible from inside the core, instead of adding another
pointe
On Monday 28 July 2003 20:53, Simon Glover wrote:
> On Mon, 28 Jul 2003, Tim Howell wrote:
> > ?tches from a few days ago to allow executable creation, the current CVS
> > no longer compiles properly on my MacOS X 10.2.6 box. The error I get
> > is:
> >
> > exec_save.c:319:16: #if with no expressi
