Re: [Algorithms] FIST optimization

[Pierre T. <p.t...@wa...>]

> Bet your Renderer->Init() function winds up loading a DLL somewhere along
> the line (for example, by initialising D3D). It's the DLL load that is
> probably whacking your FPU state.

I checked: it gets modified by the CreateDevice call. I suppose it could be
the DLL loading, yes.


> You should set the FPU state to the one you want after you do your Init().
> Thereafter, D3D won't mess with it if you set the FPU_PRESERVE flag.

That's what I do. That was exactly my question on the DXML : is that safe ?

Because:
- D3D assumes a round-to-nearest mode
- I'm changing it to chop/floor
- And as I said, FPU_PRESERVE seems only to work with the FPU precision (not
the rounding mode).

Hence the original question. Anyway, I already use your solution, and for
the moment I don't really need something else.

Pierre