> At 1:03 AM +0200 5/29/03, Leopold Toetsch wrote:
> >Luke Palmer <[EMAIL PROTECTED]> wrote:
> >
> >>  I've been trying to run pbc2c.pl, and it's been dying.  I traced the
> >>  problem down to Parrot::Packfile thinking that the size of the
> >>  bytecode segment is zero.  However, it works fine when I use
> >>  assemble.pl to compile; the problem only arises when I compile with
> >>  imcc.
> >
> >Our current problem is, that we have two assemblers and two PBC formats.
> >Keeping all in sync till now ends obviously at test level.
> >
> >But we have finally to give up assemble.pl: its slow and it doesn't
> >conform to packfile/packout.c. As previous discussions did show, we will
> >need constant/debug/fixup/... segments per bytecode file. packfile.c has
> >with the directory approach all the infrastructure. assemble.pl probably
> >doesn't keep up with that.
> >
> >I'm only waiting for tinderboxen showing imcc build and test results.
> >Before ok from these, we can't change things that need assemble.pl.
> 
> We need one more thing. The standard makefile needs to automatically 
> build imcc. Honestly I'd prefer just a single executable, named 
> parrot, that can handle assembly files, rather than the two 
> executables we're building now. If we can do that, we can ditch 
> assemble.pl.

I would totally dig that.  I use imcc for everything; why not just
call it "parrot" :-)

Luke

Reply via email to