From d5912ec7a4aff299a52b97fff0e68bb1498a6a09 Mon Sep 17 00:00:00 2001 From: Michael Tautschnig Date: Wed, 18 Nov 2020 22:12:14 +0000 Subject: [PATCH] Visual Studio 16.8 has different floating point precision GitHub action runners now feature Visual Studio 16.8.1 (previously: 16.7). According to its STL changelog, this update includes the following change: https://github.com/microsoft/STL/pull/1173#pullrequestreview-471077335 Therefore update the unit test to expect 13 trailing zeros for MSVC version >= 19.28. --- jbmc/unit/java_bytecode/expr2java.cpp | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/jbmc/unit/java_bytecode/expr2java.cpp b/jbmc/unit/java_bytecode/expr2java.cpp index 77a048c3b85..578cb9d9c2a 100644 --- a/jbmc/unit/java_bytecode/expr2java.cpp +++ b/jbmc/unit/java_bytecode/expr2java.cpp @@ -99,6 +99,10 @@ TEST_CASE( #ifndef _MSC_VER REQUIRE( floating_point_to_java_string(value) == "0x1p+37f /* 1.37439e+11 */"); +#elif _MSC_VER >= 1928 + REQUIRE( + floating_point_to_java_string(value) == + "0x1.0000000000000p+37f /* 1.37439e+11 */"); #else REQUIRE( floating_point_to_java_string(value) == @@ -112,6 +116,10 @@ TEST_CASE( #ifndef _MSC_VER REQUIRE( floating_point_to_java_string(value) == "0x1p+37 /* 1.37439e+11 */"); +#elif _MSC_VER >= 1928 + REQUIRE( + floating_point_to_java_string(value) == + "0x1.0000000000000p+37 /* 1.37439e+11 */"); #else REQUIRE( floating_point_to_java_string(value) ==