9a9ffd1370
The reason: All RunFloat64Sin/RunFloat64Cos/RunFloat64Expm1/RunFloat64Tan/Ieee754.Expm1/Ieee754.Cos/Ieee754.Tan test cases use the C++ function to generate the expected value or result. So for x87, all those expected value or result are extended double precision as the extended double precision is default for x87 Gcc compiler and std lib on linux platform. The issue is: For RunFloat64Sin/RunFloat64Cos/RunFloat64Expm1/RunFloat64Tan test cases, the expected values generated by C++ function are extended double precision, the results generated by X87 jitted code are double precision according to the ECMA standard. The comparison of different precisons caused some of those test cases failed. For Ieee754.Expm1/Ieee754.Cos/Ieee754.Tan test cases, the expected values are pre-defined double precision values, the results generated by C++ function are extended double precision. The comparison of different precisons caused some of those test cases failed too. This CL disables RunFloat64Sin/RunFloat64Cos/RunFloat64Expm1/RunFloat64Tan/Ieee754.Expm1/Ieee754.Cos/Ieee754.Tan test cases for x87. BUG= Review-Url: https://codereview.chromium.org/2111493002 Cr-Commit-Position: refs/heads/master@{#37371}
21 lines
649 B
Plaintext
21 lines
649 B
Plaintext
# Copyright 2014 the V8 project authors. All rights reserved.
|
|
# Use of this source code is governed by a BSD-style license that can be
|
|
# found in the LICENSE file.
|
|
|
|
[
|
|
['byteorder == big', {
|
|
# TODO(mips-team): Fix Wasm for big-endian.
|
|
'WasmModuleVerifyTest*': [SKIP],
|
|
'WasmFunctionVerifyTest*': [SKIP],
|
|
'WasmDecoderTest.TableSwitch*': [SKIP],
|
|
'WasmDecoderTest.AllLoadMemCombinations': [SKIP],
|
|
'AstDecoderTest.AllLoadMemCombinations': [SKIP],
|
|
'AstDecoderTest.AllStoreMemCombinations': [SKIP],
|
|
}], # 'byteorder == big'
|
|
['arch == x87', {
|
|
'Ieee754.Expm1': [SKIP],
|
|
'Ieee754.Cos': [SKIP],
|
|
'Ieee754.Tan': [SKIP],
|
|
}], # 'arch == x87'
|
|
]
|