v8/test/test262-es6
machenbach 7d02830e74 Revert of Revert "In RegExp, lastIndex is read with ToLength, not ToInteger" (patchset #1 id:1 of https://codereview.chromium.org/1243053005/)
Reason for revert:
[Sheriff] This causes a breakage with custom snapshot (bisected locally):
http://build.chromium.org/p/client.v8/builders/V8%20Linux64%20GC%20Stress%20-%20custom%20snapshot/builds/1190

Original issue's description:
> Revert "In RegExp, lastIndex is read with ToLength, not ToInteger"
>
> $toLength is slow, causing a 3.8%-8% regression in the Octane RegExp
> benchmark. Reverting this patch brings it back up. To make this change,
> we'll need a faster implementation fo $toLength.
>
> BUG=chromium:513160
> LOG=Y
> R=adamk
>
> Committed: https://crrev.com/477d651c6a978bdf34954048a235895c62dab0ac
> Cr-Commit-Position: refs/heads/master@{#29830}

TBR=adamk@chromium.org,littledan@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:513160

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

Cr-Commit-Position: refs/heads/master@{#29835}
2015-07-24 08:26:06 +00:00
..
harness-adapt.js test/test262: update testcfg.py for new test262 2014-08-22 13:00:10 +00:00
README [test262-es6] Update to 2015-07-06 which includes the yaml harness fix 2015-07-07 13:54:30 +00:00
test262-es6.status Revert of Revert "In RegExp, lastIndex is read with ToLength, not ToInteger" (patchset #1 id:1 of https://codereview.chromium.org/1243053005/) 2015-07-24 08:26:06 +00:00
testcfg.py [test262-es6] Update to 2015-07-06 which includes the yaml harness fix 2015-07-07 13:54:30 +00:00

This directory contains code for binding the test262 test suite
into the v8 test harness. To use the tests check out the test262
tests from

  https://github.com/tc39/test262

at hash c6ac390 (2015/07/06 revision) as 'data' in this directory.  Using later
version may be possible but the tests are only known to pass (and indeed run)
with that revision.

  git clone https://github.com/tc39/test262 data
  cd data
  git checkout c6ac390

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.