Commit ee4225fd authored by mstarzinger's avatar mstarzinger Committed by Commit bot

[interpreter] Remove wholesale skipping of strong mode tests.

By now the deprecation of strong mode is far enough along that the
support present in the interpreter matches the support in the other
compilers. Special expectations aren't needed anymore.

R=rmcilroy@chromium.org

Review URL: https://codereview.chromium.org/1738653003

Cr-Commit-Position: refs/heads/master@{#34293}
parent 19bad8a9
......@@ -1468,9 +1468,8 @@ Bytecode BytecodeArrayBuilder::BytecodeForStoreIC(LanguageMode language_mode) {
case SLOPPY:
return Bytecode::kStoreICSloppy;
case STRICT:
return Bytecode::kStoreICStrict;
case STRONG:
UNIMPLEMENTED();
return Bytecode::kStoreICStrict;
default:
UNREACHABLE();
}
......@@ -1485,9 +1484,8 @@ Bytecode BytecodeArrayBuilder::BytecodeForKeyedStoreIC(
case SLOPPY:
return Bytecode::kKeyedStoreICSloppy;
case STRICT:
return Bytecode::kKeyedStoreICStrict;
case STRONG:
UNIMPLEMENTED();
return Bytecode::kKeyedStoreICStrict;
default:
UNREACHABLE();
}
......
......@@ -537,10 +537,6 @@
'test-inobject-slack-tracking/JSGeneratorObjectBasicNoInlineNew': [FAIL],
'test-api/IsGeneratorFunctionOrObject': [FAIL],
# TODO(rmcilroy,4680): Strong mode failures.
'test-api/AccessorShouldThrowOnError': [FAIL],
'test-api/InterceptorShouldThrowOnError': [FAIL],
# TODO(rmcilroy,4680): The function_data field should be a BytecodeArray on interpreter entry
'test-api/SetFunctionEntryHook': [FAIL],
......
......@@ -773,9 +773,6 @@
}], # 'arch == ppc and simulator_run == True'
['ignition == True', {
# Skip strong mode tests since strong mode is unsupported on ignition.
'strong/*': [SKIP],
# TODO(yangguo,4690): Requires debugger support.
'es6/debug*': [SKIP],
'harmony/debug*': [SKIP],
......@@ -859,6 +856,8 @@
'harmony/iterator-close': [FAIL],
'harmony/reflect-construct': [FAIL],
'es6/promises': [FAIL],
'strong/function-arity': [FAIL],
'strong/undefined': [FAIL],
# TODO(rmcilroy,4680): Pass on debug, fail on release. Fails in both modes.
# the line numbers in the stack trace are incorrect. In debug mode somehow
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment