Re: signal 11 when run on x86, JIT enabled

2002-10-15 Thread Leopold Toetsch
Steve Fink wrote: > On Mon, Oct 14, 2002 at 10:06:54AM +0200, Leopold Toetsch wrote: >>This is, what restart NEXT() does. >> > > That's what I originally thought, but there seemed to be no attempt at > implementing this in the code, so I though it must not have been > attempted yet -- hence the

Re: signal 11 when run on x86, JIT enabled

2002-10-15 Thread Steve Fink
On Mon, Oct 14, 2002 at 10:06:54AM +0200, Leopold Toetsch wrote: > Steve Fink wrote: > > > >The problem is that the JIT doesn't support tracing. > > > No, the problem is, that restarting JIT is broken. So it's truely a bug > and should not be marked with SKIP or TODO. > > >... I could imagi

Re: signal 11 when run on x86, JIT enabled

2002-10-14 Thread Leopold Toetsch
Steve Fink wrote: > The problem is that the JIT doesn't support tracing. No, the problem is, that restarting JIT is broken. So it's truely a bug and should not be marked with SKIP or TODO. > ... I could imagine > ways of fixing this -- make it drop into a non-JIT core if tracing is > turned

RE: signal 11 when run on x86, JIT enabled

2002-10-13 Thread Brent Dax
Simon Glover: # On Sun, 13 Oct 2002, Steve Fink wrote: # Your problem was probably forgetting to use Test::More # (which defines skip). In any case, the enclosed patch should # do the trick. # # +SKIP: { skip("Doesn't work with JIT enabled", 1); # output_like(<<'CODE', <<'OUTPUT', "restart t

Re: signal 11 when run on x86, JIT enabled

2002-10-13 Thread Simon Glover
On Sun, 13 Oct 2002, Steve Fink wrote: [Discussion snipped] > Yes, I get this also. I was trying to figure out how to properly use > TODO or SKIP or something to suppress this, but none of them worked > quite right -- it would say that the failed test was a TODO, but it > still counted it as a

Re: signal 11 when run on x86, JIT enabled

2002-10-13 Thread Steve Fink
On Sun, Oct 13, 2002 at 11:08:02PM +0100, Nicholas Clark wrote: > On Sun, Oct 13, 2002 at 03:06:48AM -0700, Steve Fink wrote: > > On Fri, Oct 11, 2002 at 05:05:56PM -0700, Joe Wilson wrote: > > > Perhaps this is a known issue... > > > > > > Most parrot programs seem to crash on x86 when the lates

Re: signal 11 when run on x86, JIT enabled

2002-10-13 Thread Nicholas Clark
On Sun, Oct 13, 2002 at 03:06:48AM -0700, Steve Fink wrote: > On Fri, Oct 11, 2002 at 05:05:56PM -0700, Joe Wilson wrote: > > Perhaps this is a known issue... > > > > Most parrot programs seem to crash on x86 when the latest CVS parrot > > is compiled with "-O2" or "-g -O2" and when JIT is enabl

Re: signal 11 when run on x86, JIT enabled

2002-10-13 Thread Steve Fink
On Fri, Oct 11, 2002 at 05:05:56PM -0700, Joe Wilson wrote: > Perhaps this is a known issue... > > Most parrot programs seem to crash on x86 when the latest CVS parrot > is compiled with "-O2" or "-g -O2" and when JIT is enabled. > The programs appear to run to completion and only crash prior to