On Wed, Nov 30, 2005 at 08:05:09AM -0800, jerry gay wrote: > On 11/30/05, Peter Sinnott <[EMAIL PROTECTED]> wrote: > > On Wed, Nov 30, 2005 at 03:49:36PM -0000, Jonathan Worthington wrote: > > > OK, attached. If you run this as a PIR example, it works just fine. If > > > you compile it to a PBC, then you get the error. > > > > > > $ parrot breaks2.pir example.dll > > > > > > $ parrot -o breaks2.pbc breaks2.pir > > > > > > $ parrot breaks2.pbc example.dll > > > directory_pack segment 'BYTECODE_EVAL_1' used size 158 but reported 160 > > > > > > Note: example.dll need not exist. Sorry it's not a particularly small > > > test > > > case - the problem seemed to vanish when I simplified it further than I > > > have. > > > > > > > Might this be related to bug 32392? > > > > http://rt.perl.org/rt3/index.html?q=32392 > > > if you mean GETARGS: and GOTARGS:, no, they're not duplicates ;) >
GETARGS GOTARGS? I have no idea what your talking about I was refering to the bug that said : "Also label fixup handling is different so just don't compile PIR files to PASM except for debugging" and wondering if whatever caused pir->pasm->execute pasm to not always work also caused pir->pbc->execute pbc to not always work. > ~jerry -- The customer can count on us to seamlessly promote corporate intellectual capital to allow us to collaboratively restore business methods of empowerment
