v8/test262 at 847ac580f15edf36aa2f2bf0735ac0013c912a19 - v8

History

mstarzinger 0b3066b8f5 [interpreter] First implementation of stack unwinding. This implements a first prototype of stack unwinding for interpreted frames. The unwinding machinery performs a range-based lookup in the given handler table and potentially continues dispatching at the handler offset. Note that this does not yet correctly restore the context to the correct value when the handler is being entered. R=rmcilroy@chromium.org,oth@chromium.org BUG=v8:4674 LOG=n Review URL: https://codereview.chromium.org/1605633003 Cr-Commit-Position: refs/heads/master@{#33414}		2016-01-20 18:10:40 +00:00
..
harness-adapt.js	[test] Copy test262-es6 into test262.	2015-09-25 13:03:36 +00:00
README	Make test262 README file revision independent.	2015-11-04 10:52:44 +00:00
test262.gyp	[swarming] Isolate test262.	2015-10-14 08:44:27 +00:00
test262.isolate	[swarming] Isolate test262.	2015-10-14 08:44:27 +00:00
test262.status	[interpreter] First implementation of stack unwinding.	2016-01-20 18:10:40 +00:00
testcfg.py	[Interpreter]: Add ignition blacklist to mjsunit.status and test262.status.	2015-11-06 18:52:51 +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.