Why does we still need StrictMath?

Victor Williams Stafusa da Silva victorwssilva at gmail.com
Sun May 8 12:15:38 UTC 2022


Was that using Java 17+, which included JEP 306 delivered?

Em dom., 8 de mai. de 2022 às 08:10, Martin Desruisseaux <
martin.desruisseaux at geomatys.com> escreveu:

> Le 08/05/2022 à 10:56, Andrew Haley a écrit :
>
> > Some targets (x86, in particular) have intrinsics (log, trig) that are
> > faster than StrictMath and also more accurate. StrictMath is not about
> > accuracy, but cross-architecture down-to-the-last bit reproducibility.
> > Whether we still need that reproducibility is, I suppose, something
> > for debate.
> >
> In production code, maybe not. But in test code (e.g. using JUnit), when
> the program does a lot of trigonometric operations (e.g. map
> projections), I have meet cases where a test was successful on a machine
> but failed on another machine. The systematic use of StrictMath in all
> JUnit test code ensure that the difference in behavior is not in the
> test code, so we can focus our debugging effort on the main code.
>
>      Martin
>
>
>


More information about the core-libs-dev mailing list