You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Checks when running "test-conversions", "test-ieee" and "test-strtod" fail, which is pretty much expected, since the fast floating-point behavior is deliberately imprecise.
Should the library force "/fp:precise" behavior using the following pragma? Or shall it be up to the user to choose the correct floating-point behavior? In that case it would be good to add this to the documentation.
#pragma float_control(precise, on, push)
...
#pragma float_control(pop)
The text was updated successfully, but these errors were encountered:
It seems like there are some tests in "test-strtod" that fail even with "/fp:precise". I see that some checks are already disabled for MSVC... maybe a few more need to be disabled as well. I'm using Visual Studio 2013 / 12.0.31101.00 Update 4
I currently don't have a Windows machine handy. Could you send me the tests that fail?
The tests that currently fail are errors during compile-time of the MSVC. That is, it reads some numbers the wrong way. So far there isn't any test that fails because it produces incorrect code.
thanks.
Checks when running "test-conversions", "test-ieee" and "test-strtod" fail, which is pretty much expected, since the fast floating-point behavior is deliberately imprecise.
See documentation here: https://msdn.microsoft.com/en-us/library/e7s85ffb.aspx
Should the library force "/fp:precise" behavior using the following pragma? Or shall it be up to the user to choose the correct floating-point behavior? In that case it would be good to add this to the documentation.
The text was updated successfully, but these errors were encountered: