Skip to content

V
V8
Switch branch/tag
  1. 26 Feb, 2016 1 commit
    • bmeurer's avatar
      [runtime] Remove obsolete %Apply and %TailCall runtime entries. · 7f11fba7
      bmeurer authored 
      The %TailCall runtime entry and the %_TailCall intrinsic is not used,
and will never be used (because %TailCall doesn't actually do a tail
call). We will soon have proper ES6 tail calls, which are correct and
properly tested.

The %Apply runtime entry is basically a super-slow, less correct version
of Reflect.apply, so we can as well just use Reflect.apply, which is
exposed to builtins via %reflect_apply.

R=ishell@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#34317}
      7f11fba7
  3. 18 Feb, 2016 2 commits
    • adamk's avatar
      Remove strong mode support from Scope and Variable · 63efda35
      adamk authored 
      This frees up one bit in FunctionKind, which I plan to make slightly
more syntactic info about functions available in SharedFunctionInfo
(needed for ES2015 Function.name support).

BUG=v8:3956, v8:4760
LOG=n

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

Cr-Commit-Position: refs/heads/master@{#34125}
      63efda35
    • rossberg's avatar
      [es6] Implement for-of iterator finalization · cb1bf4af
      rossberg authored 
      Implements iterator finalisation by desugaring for-of loops with an additional try-finally wrapper. See comment in parser.cc for details.

Also improved some AST printing facilities while there.

@Ross, I had to disable the bytecode generation test for for-of, because it got completely out of hand after this change (the new bytecode has 150+ lines). See the TODO that I assigned to you.

Patch set 1 is WIP patch by Georg (http://crrev.com/1695583003), patch set 2 relative changes.

@Georg, FYI, I changed the following:

- Moved try-finally out of the loop body, for performance, and in order to be able to handle `continue` correctly.
- Fixed scope management in ParseForStatement, which was the cause for the variable allocation failure.
- Fixed pre-existing zone initialisation bug in rewriter, which caused the crashes.
- Enabled all tests, adjusted a few others, added a couple more.

BUG=v8:2214
LOG=Y

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

Cr-Commit-Position: refs/heads/master@{#34111}
      cb1bf4af
  5. 12 Dec, 2015 1 commit
  7. 07 Dec, 2015 1 commit
  9. 18 Nov, 2015 1 commit
  11. 13 Nov, 2015 1 commit
  13. 12 Nov, 2015 1 commit
  15. 05 Nov, 2015 1 commit
  17. 28 Oct, 2015 1 commit
  19. 30 Sep, 2015 1 commit
  21. 28 Sep, 2015 1 commit
  23. 22 Sep, 2015 1 commit
  25. 08 Sep, 2015 1 commit
    • bmeurer's avatar
      [runtime] Replace many buggy uses of %_CallFunction with %_Call. · db2ba190
      bmeurer authored 
      The semantics of the %_CallFunction intrinsic seem to be very unclear,
which resulted in a lot of bugs. Especially the combination with
%IsSloppyModeFunction is always a bug, because the receiver would be
wrapped in the wrong context. So the %IsSloppyModeFunction helper is
gone now, and many of the buggy uses of %_CallFunction are also
eliminated.

If you ever need to call something with a different receiver, then
%_Call is your friend now. It does what you want and implements the
call sequence fully (and correct).

BUG=v8:4413
LOG=n

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

Cr-Commit-Position: refs/heads/master@{#30634}
      db2ba190
  27. 02 Sep, 2015 1 commit
  29. 01 Sep, 2015 1 commit
  31. 26 Aug, 2015 1 commit
  33. 05 Aug, 2015 2 commits
  35. 16 Jul, 2015 1 commit
  37. 14 Jul, 2015 1 commit
  39. 13 Jul, 2015 2 commits
  41. 02 Jul, 2015 2 commits
  43. 01 Jul, 2015 1 commit
  45. 30 Jun, 2015 4 commits
  47. 26 Jun, 2015 1 commit
  49. 19 Jun, 2015 1 commit
  51. 18 Jun, 2015 3 commits
  53. 02 Jun, 2015 1 commit
  55. 01 Jun, 2015 1 commit
    • conradw's avatar
      [strong] Implement per-object restrictions behaviour of delete operator · b14305c1
      conradw authored 
      Implements the strong mode proposal's restrictions on the behaviour of the
delete operator for strong objects.

Setting the strong bit is still wip, so this change will only affect those
objects that have the bit correctly set. The tests reflect this, and will be
expanded as more objects can be marked as strong.

Attempt 2, last version did not work with API.

BUG=v8:3956
LOG=N

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

Cr-Commit-Position: refs/heads/master@{#28724}
      b14305c1
  57. 29 May, 2015 1 commit
  59. 27 May, 2015 2 commits