Skip to content

V
V8
Switch branch/tag
  1. 21 Mar, 2016 1 commit
  3. 18 Mar, 2016 1 commit
  5. 10 Mar, 2016 1 commit
  7. 16 Dec, 2015 1 commit
  9. 12 Dec, 2015 1 commit
  11. 11 Dec, 2015 1 commit
  13. 10 Dec, 2015 1 commit
    • littledan's avatar
      Unstage non-standard Promise functions · 88c8361b
      littledan authored 
      This patch removes Promise functions and methods which are absent
from the ES2015 specification when the --es-staging flag is on.
The patch is being relanded after being reverted due to an
unrelated bug. This version is slightly different as promise_chain
is installed on the context regardless of the flag value, so that
the Promise::Chain API continues to work until it is deprecated.

BUG=v8:3237
R=rossberg
LOG=Y

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

Cr-Commit-Position: refs/heads/master@{#32772}
      88c8361b
  15. 03 Dec, 2015 1 commit
    • mstarzinger's avatar
      [fullcode] Switch passing of new.target to register. · 440a42b7
      mstarzinger authored 
      This passes the new.target value in a register instead of through a
side-channel via the construct stub. Note that this marks the last
consumer of said side-channel and the special slot in the construct
stub frame can be removed as a follow-up.

R=bmeurer@chromium.org,yangguo@chromium.org
TEST=mjsunit/es6/regress/regress-new-target-context

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

Cr-Commit-Position: refs/heads/master@{#32548}
      440a42b7
  17. 02 Dec, 2015 1 commit
  19. 01 Dec, 2015 1 commit
  21. 24 Nov, 2015 3 commits
  23. 18 Nov, 2015 1 commit
  25. 13 Nov, 2015 1 commit
  27. 29 Oct, 2015 1 commit
  29. 28 Oct, 2015 1 commit
  31. 07 Oct, 2015 1 commit
    • adamk's avatar
      Use Scope::function_kind_ to distinguish arrow function scopes · 24565b85
      adamk authored 
      Previously, arrow function scopes had a separate ScopeType. However,
Scope::DeserializeScopeChain() erroneously deserialized ARROW_SCOPE
ScopeInfos as FUNCTION_SCOPE. This could lead to bugs such as the
attached one, where "super" was disallowed where it should have
been allowed.

This patch utilizes the Scope's FunctionKind to distinguish arrow
functions from others. Besides fixing the above bug, this also
simplifies code in various places that had to deal with two different
ScopeTypes both of which meant "function".

BUG=v8:4466
LOG=n

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

Cr-Commit-Position: refs/heads/master@{#31154}
      24565b85
  33. 30 Sep, 2015 1 commit
  35. 24 Aug, 2015 1 commit
  37. 04 Aug, 2015 1 commit
  39. 23 Jul, 2015 1 commit
  41. 01 Jul, 2015 1 commit
  43. 26 Jun, 2015 1 commit
  45. 11 Jun, 2015 1 commit
  47. 12 May, 2015 2 commits
  49. 05 May, 2015 1 commit
    • dslomov's avatar
      Handle the case when derived constructor is [[Call]]ed with 0 args. · cf53fed9
      dslomov authored 
      ArgumentsAdaptorStub for derived constructor (the one that needs
new.target) works in this way:
 - If the constructor is invoked via the Construct stub, we know that
   actual arguments always include new.target. ``arguments`` object
   however should not include a new.target, therefore we remove it.
   We achieve this by decrementing the argument count.
 - If the constructor is invoked as a call, we do not care for a correct
   ``arguments`` array since the constructor will immediately throw on
   entrance.
The bug is that the call could actually pass 0 actual arguments, but I
decrement unconditionally :(. The fix is to detect this case and avoid
decrementing. ``arguments`` is bogus, but it is ok as constructor
throws.

Long-term we should just remove mucking about with arguments for
new.target and just get it from the stack.

R=arv@chromium.org,rossberg@chromium.org
BUG=chromium:474783
LOG=Y

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

Cr-Commit-Position: refs/heads/master@{#28242}
      cf53fed9
  51. 22 Apr, 2015 1 commit
  53. 27 Mar, 2015 1 commit
    • dslomov's avatar
      Make sure debugger is ready for breakpoins when we process 'debugger' statement. · 15ef61d4
      dslomov authored 
      On 'debugger' statement, if anything in debugger calls 'EnsureDebugInfo'
on a function, EnsureDebugInfo would compile and substitute code without
debug break slots. This causes weird behavior later when stepping fails
to work (see added test as an example).
This fix is to make sure the debugger is prepared for breakpoints in
that case as well.

Also adds extra testing for bug 468661.

R=yangguo@chromium.org,yurys@chromium.orh
BUG=v8:3990,chromium:468661
LOG=N

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

Cr-Commit-Position: refs/heads/master@{#27502}
      15ef61d4
  55. 24 Mar, 2015 1 commit
    • dslomov's avatar
      Do not assign positions to parser-generated desugarings. · 49c3a606
      dslomov authored 
      The root cause for the bug is that the positions assigned to desugared
code was inconsistent with the source ranges of block scopes.
Since the fact that the position is assigned causes the debugger to
break at the parser-generated statement, the fix is to remove positions
from those nodes that we do not want to break on.

The CL also teaches Hydrogen to tolerate these cases.

R=adamk@chromium.org,rossberg@chromium.org
BUG=chromium:468661
LOG=Y

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

Cr-Commit-Position: refs/heads/master@{#27424}
      49c3a606
  57. 20 Mar, 2015 1 commit
  59. 13 Mar, 2015 1 commit
  61. 03 Mar, 2015 1 commit
  63. 19 Feb, 2015 1 commit
  65. 16 Sep, 2014 1 commit
  67. 21 Aug, 2014 1 commit
  69. 07 Aug, 2014 1 commit
  71. 05 Aug, 2014 1 commit
  73. 04 Aug, 2014 1 commit