Skip to content

Commit d5912ec

Browse files
committed
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: microsoft/STL#1173 (review) Therefore update the unit test to expect 13 trailing zeros for MSVC version >= 19.28.
1 parent 299307b commit d5912ec

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

jbmc/unit/java_bytecode/expr2java.cpp

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,10 @@ TEST_CASE(
9999
#ifndef _MSC_VER
100100
REQUIRE(
101101
floating_point_to_java_string(value) == "0x1p+37f /* 1.37439e+11 */");
102+
#elif _MSC_VER >= 1928
103+
REQUIRE(
104+
floating_point_to_java_string(value) ==
105+
"0x1.0000000000000p+37f /* 1.37439e+11 */");
102106
#else
103107
REQUIRE(
104108
floating_point_to_java_string(value) ==
@@ -112,6 +116,10 @@ TEST_CASE(
112116
#ifndef _MSC_VER
113117
REQUIRE(
114118
floating_point_to_java_string(value) == "0x1p+37 /* 1.37439e+11 */");
119+
#elif _MSC_VER >= 1928
120+
REQUIRE(
121+
floating_point_to_java_string(value) ==
122+
"0x1.0000000000000p+37 /* 1.37439e+11 */");
115123
#else
116124
REQUIRE(
117125
floating_point_to_java_string(value) ==

0 commit comments

Comments
 (0)