Re: [Mingw-w64-public] bug in sin(pi) ?

On Fri, Jun 11, 2021 at 1:22 AM LRN wrote: > On 10.06.2021 10:03, Liu Hao wrote: > [snip] > > Before doing that, I would like to ask, does the inaccuracy really > matter? > > I always assumed that when dealing with floating-point math there's no > such > thing as "yielding precisely this number".

Re: [Mingw-w64-public] [PATCH] crt: Don't initialize lconv to unsigned char mode

在 6/11/21 4:09 AM, Martin Storsjö 写道: Since the initial commit of mingw-w64, there's a call (in a constructor in crt/charmax.c, pulled in via the mingw_initcharmax variable) to __lconv_init(), which reconfigures the CRT's lconv info to unsigned char mode - but there's no explanation for why this

[Mingw-w64-public] [PATCH] crt: Don't initialize lconv to unsigned char mode

Since the initial commit of mingw-w64, there's a call (in a constructor in crt/charmax.c, pulled in via the mingw_initcharmax variable) to __lconv_init(), which reconfigures the CRT's lconv info to unsigned char mode - but there's no explanation for why this is the case. The fact that mingw-w64 in

Re: [Mingw-w64-public] bug in sin(pi) ?

On 10.06.2021 10:03, Liu Hao wrote: 在 6/10/21 1:40 AM, Carl Kleffner 写道: This behaviour is described here: Intel Underestimates Error Bounds by 1.3 quintillion in great detail. A possible soluti

Re: [Mingw-w64-public] bug in sin(pi) ?

在 6/10/21 1:40 AM, Carl Kleffner 写道: This behaviour is described here: Intel Underestimates Error Bounds by 1.3 quintillion in great detail. A possible solution could be the usage of the SLEEF Ve