At 11:54 AM 10/12/2001 -0400, Gregor N. Purdy wrote:
>Dan --
>
> > >There has got to be something stupid I've done in these big changes,
> > >but I can't think of a failure mode that would screw up floor().
> >
> > My bet, if I had to bet, is that it's not floor that's messed up. You
> might
> > want to build parrot with debugging and step through and see if maybe the
> > stack's getting trashed so printf's getting crap passed in or something
> > like that.
>
>That sounds reasonable. I recompiled with -g and set a breakpoint on
>Parrot_floortest and stepped through it. gdb didn't complain, but
>right after the floor() call, the variable had the wacky value.
It's also possible the 0.0/3.0 division's getting things messed up
depending on what flags are set during the compile. It ought to be 0, but
there might be some NaNs sneaking in or something.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
