4bd1215c95
Recent versions of the Windows Universal CRT changed the behavior of fmod for when the first parameter is negative. In particular, a result of negative zero became positive zero. This is rarely critical but it causes test failures and may effect some JS test suites or web pages. The fix is to modify Modulo to check for a result of 0 when the first parameter is negative and change the result to -0. That fixes four of the five test failures and the fifth one is fixed by comparing the results against Modulo instead of std::fmod. Bug: chromium:915045 Change-Id: Ia4490ec98361a37006d6c338acd33f959fa3ccea Reviewed-on: https://chromium-review.googlesource.com/c/1383091 Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#58377} |
||
|---|---|---|
| .. | ||
| bytecode_expectations | ||
| bytecode-expectations-printer.cc | ||
| bytecode-expectations-printer.h | ||
| generate-bytecode-expectations.cc | ||
| interpreter-tester.cc | ||
| interpreter-tester.h | ||
| source-position-matcher.cc | ||
| source-position-matcher.h | ||
| test-bytecode-generator.cc | ||
| test-interpreter-intrinsics.cc | ||
| test-interpreter.cc | ||
| test-source-positions.cc | ||