v8/test262 at 86d0dd362f627a7831b042d4fe8baa121c976fc4 - v8

History

caitp 86d0dd362f [builtins] implement Array.prototype[@@iterator] in TFJ builtins Implements the variations of CreateArrayIterator() in TFJ builtins (ArrayPrototypeValues, ArrayPrototypeEntries and ArrayPrototypeKeys), and provides two new Object types with numerous maps which identify certain behaviours, which will be useful for inlining. Removes src/js/array-iterator.js entirely Also adds support for printing Symbol literals inserted by the Parser during desugaring when FLAG_print_builtin_ast is set to true. BUG=v8:5388 R=bmeurer@chromium.org, cbruni@chromium.org TBR=ulan@chromium.org Review-Url: https://codereview.chromium.org/2405253006 Cr-Commit-Position: refs/heads/master@{#40373}		2016-10-18 02:43:14 +00:00
..
archive.py	[test262] Use standalone Test262 harness project	2016-07-22 15:25:32 +00:00
BUILD.gn	[gn] Port test262 archiving to gn	2016-06-06 08:56:58 +00:00
detachArrayBuffer.js	This patch updates to the latest test262 version	2016-09-01 17:43:31 +00:00
harness-adapt.js	This patch updates to the latest test262 version	2016-09-01 17:43:31 +00:00
list.py	[test262] Use standalone Test262 harness project	2016-07-22 15:25:32 +00:00
README	Make test262 README file revision independent.	2015-11-04 10:52:44 +00:00
test262.gyp	[gn] Move build to gypfiles	2016-04-29 10:11:11 +00:00
test262.isolate	test262 roll	2016-05-02 23:02:38 +00:00
test262.status	[builtins] implement Array.prototype[@@iterator] in TFJ builtins	2016-10-18 02:43:14 +00:00
testcfg.py	[modules] Update test262 config and status file.	2016-10-10 17:38:56 +00:00

README

This directory contains code for binding the test262 test suite
into the v8 test harness. The tests are checked out as a dependency from

  https://chromium.googlesource.com/external/github.com/tc39/test262

at a revision specified in the DEPS file as 'data' in this directory. They are
fetched with 'gclient sync'. To update to a newer version, please change the
DEPS file.

Using a newer version, e.g. 'deadbeef' may be possible but the tests are only
known to pass (and indeed run) with the DEPS revision. Example:

  cd data
  git fetch
  git checkout deadbeef

If you do update to a newer revision you may have to change the test
harness adapter code since it uses internal functionality from the
harness that comes bundled with the tests.  You will most likely also
have to update the test expectation file.