Re: control that floating point [was: Re: single precision]

[Ashwin Hirschi <deery@...>]

> > A good debugging tool in this situation is to turn on FPU exceptions,
> > and run in the debugger.  It should break on the line that does an
> > invalid op.  Assuming that's what's going on.  Might help you, might
> > not, but when it helps it really helps.
>
> I may be misremembering here:
>
> Doesn't IA32 have some crufty FPU flag that means "Yes, I really want all my floating point exceptions to occur on the instruction that caused them and not the next FPU instruction that I execute which could well be after a branch or a function return".  You want to switch that on too.

This is VERY true: the delayed FP exceptions sure threw me for a loop, since the places where the exceptions occured had little to do with the actual (external) code that caused them.

I should have mentioned this in my original posting. That's repressed bad memories for you... So it's a good thing you bring it up, David!

Ashwin.
--
no signature is a signature