v8/test262 at e10fdbed6d8b0ccbb3b4938bf6b3970b01cff2e8 - v8

History

mythria e7373f4285 [Interpreter] Allocates new temporary register outside the reservation for consecutive registers. Consecutive registers are allocated in two passes. First we "reserve" a set of registers and these get allocated when we actually use them. If we request for a temporary register before we use all the consecutive registers, the earlier implementation does not gaurantee that it allocates outside the reservation for consecutive registers. This could cause problems for example, in call_func(a, b++, c). This cl fixes TemporaryRegisterScope::NewRegister, to return a new temporary register outside the reservation for consecutive registers. BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1531273002 Cr-Commit-Position: refs/heads/master@{#33005}		2015-12-22 09:26:25 +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] Allocates new temporary register outside the reservation for consecutive registers.	2015-12-22 09:26:25 +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.