Re: Packfile writing bug

2005-12-02 Thread Jonathan Worthington
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote: Jonathan Worthington wrote: $ parrot -o breaks2.pbc breaks2.pir $ parrot breaks2.pbc example.dll directory_pack segment 'BYTECODE_EVAL_1' used size 158 but reported 160 Same answer as Jerry - works here on x86/linux. Ugh. And if I build Parrot o

Re: Packfile writing bug

2005-11-30 Thread Leopold Toetsch
On Nov 30, 2005, at 18:04, Peter Sinnott wrote: 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" That is a bug related to printing PIR -> PASM and compiling the output (which is still avtive, but unch

Re: Packfile writing bug

2005-11-30 Thread Peter Sinnott
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 -, Jonathan Worthington wrote: > > > OK, attached. If you run this as a PIR example, it works just fine. If > > > you compile it to a PBC,

Re: Packfile writing bug

2005-11-30 Thread Leopold Toetsch
Jonathan Worthington wrote: $ parrot -o breaks2.pbc breaks2.pir $ parrot breaks2.pbc example.dll directory_pack segment 'BYTECODE_EVAL_1' used size 158 but reported 160 Same answer as Jerry - works here on x86/linux. Thanks, Jonathan leo

Re: Packfile writing bug

2005-11-30 Thread jerry gay
On 11/30/05, Jonathan Worthington <[EMAIL PROTECTED]> wrote: > "Leopold Toetsch" <[EMAIL PROTECTED]> wrote: > > Jonathan Worthington wrote: > >> Hi, > >> > >> I seem to be touching a bug related to writing compiled code. > >> i can't recreate this bug (r10271). D:\usr\local\parrot\trunk>parrot br

Re: Packfile writing bug

2005-11-30 Thread jerry gay
On 11/30/05, Peter Sinnott <[EMAIL PROTECTED]> wrote: > On Wed, Nov 30, 2005 at 03:49:36PM -, 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 >

Re: Packfile writing bug

2005-11-30 Thread Peter Sinnott
On Wed, Nov 30, 2005 at 03:49:36PM -, 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.p

Re: Packfile writing bug

2005-11-30 Thread Jonathan Worthington
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote: Jonathan Worthington wrote: Hi, I seem to be touching a bug related to writing compiled code. pir_comp = compreg "PIR" pbc_out = pir_comp(gen_pir) fh = open output print fh, pbc_out close fh On the print line, I get this error:- directory_pack seg

Re: Packfile writing bug

2005-11-30 Thread Leopold Toetsch
Jonathan Worthington wrote: Hi, I seem to be touching a bug related to writing compiled code. pir_comp = compreg "PIR" pbc_out = pir_comp(gen_pir) fh = open output print fh, pbc_out close fh On the print line, I get this error:- directory_pack segment 'BYTECODE_EVAL_1' used size 158 but repor

Packfile writing bug

2005-11-29 Thread Jonathan Worthington
Hi, I seem to be touching a bug related to writing compiled code. pir_comp = compreg "PIR" pbc_out = pir_comp(gen_pir) fh = open output print fh, pbc_out close fh On the print line, I get this error:- directory_pack segment 'BYTECODE_EVAL_1' used size 158 but reported 160 This used to work -