Okay, I can confirm the bug is fixed.
It's insane this bug did not cause any more problems. Every call into every
C function that uses floating point could have been affected (OpenGL, BLAS,
etc)
On Fri, Apr 3, 2009 at 10:47 PM, Peter Verswyvelen wrote:
> Ouch, what a waste of time on
t case now. Will certainly test this
with GHC 6.10.2.
On Fri, Apr 3, 2009 at 10:35 PM, Ian Lynagh wrote:
> On Fri, Apr 03, 2009 at 10:10:17PM +0200, Peter Verswyvelen wrote:
> > I tried both precise and fast, but that did not help. Compiling to SSE2
> > fixed it, since that does n
t at least it might be helpful to
> know if changing the floating point model causes the bug to go away.
>
>
> On Fri, Apr 3, 2009 at 2:31 PM, Peter Verswyvelen wrote:
>
>> Well this situation can indeed not occur on PowerPCs since these CPUs just
>> have floating point r
, but on Intel they
> sometimes are.
>
> Regards,
> Malcolm
>
>
> On 3 Apr 2009, at 18:58, Peter Verswyvelen wrote:
>
> For days I'm fighting against a weird bug.
>>
>> My Haskell code calls into a C function residing in a DLL (I'm on Windows,
>&g
