Skip to content

V
V8
Switch branch/tag
  1. 29 Jun, 2016 1 commit
  3. 06 Jun, 2016 1 commit
    • jochen's avatar
      Add a convenience method to get the debugged context · 37394eb3
      jochen authored 
      Since the generic GetCallingContext is deprecated, but there's still the
use case for the debugger to get the currently debugged context while in
the debug context, add a convenience API for it.

Note that EventDetails already exposes this context, but the embedder
might not necessarily have the EventDetails around.

R=verwaest@chromium.org
BUG=

Review-Url: https://codereview.chromium.org/2040853003
Cr-Commit-Position: refs/heads/master@{#36751}
      37394eb3
  5. 31 May, 2016 2 commits
  7. 24 May, 2016 1 commit
    • jgruber's avatar
      Refactor script position calculation · 94ad3b18
      jgruber authored 
      Script position calculation logic (i.e. line & column numbers for a
given code position) is now based on a single method
Script::GetPositionInfo(). Refactored related code in isolate.cc and
js/messages.js to use the new method. The line_ends accessor is still
in use by chromium and thus cannot be removed yet.

R=yangguo@chromium.org
BUG=

Review-Url: https://codereview.chromium.org/2002993002
Cr-Commit-Position: refs/heads/master@{#36458}
      94ad3b18
  9. 20 May, 2016 2 commits
  11. 19 May, 2016 2 commits
  13. 18 May, 2016 2 commits
  15. 11 May, 2016 1 commit
    • littledan's avatar
      Unship V8 custom Promise methods · fa160602
      littledan authored 
      The data from UseCounters are in--V8's custom Promise methods are not
in wide use on the web (<.002%). Therefore, this patch removes them.
That includes:
- Promise.prototype.chain
- Promise.defer -- the most widely used of the bunch
- Promise.accept

For now, those methods are still available by checking the "disable
latest stable JavaScript features" flag, or --promise-extra at the
command line, but I expect them to be fully removable.

R=adamk
CC=rossberg
BUG=v8:3238,v8:4633

Review-Url: https://codereview.chromium.org/1965183002
Cr-Commit-Position: refs/heads/master@{#36152}
      fa160602
  17. 22 Apr, 2016 1 commit
  19. 19 Apr, 2016 1 commit
  21. 04 Apr, 2016 1 commit
  23. 30 Mar, 2016 1 commit
  25. 15 Mar, 2016 1 commit
  27. 11 Mar, 2016 1 commit
    • vogelheim's avatar
      Fix expression positions for for-loops. · de4f3d3e
      vogelheim authored 
      FullCodegen generates 2 statement positions for the loop init block, like so:

  for(var i = 0; i....
      ^   ^

This change removes the first of those, updates unit tests,
and removes text expectations for Ignition.

---
An alternative would be to emulate the existing behaviour in Ignition, but:
- The new behaviour seems more logical,
- Ignition generates no bytecodes for the 'var', meaning there is no code position to attach the break position to.

BUG=v8:4690
LOG=Y

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

Cr-Commit-Position: refs/heads/master@{#34717}
      de4f3d3e
  29. 07 Mar, 2016 3 commits
  31. 01 Mar, 2016 1 commit
    • yangguo's avatar
      [debugger] fix break locations for assignments and return. · d9fe836d
      yangguo authored 
      We used to emit debug break location on block entry. This cannot be
ported to the interpreted as we do not emit bytecode for block entry.
This made no sense to begin with though, but accidentally added
break locations for var declarations.

With this change, the debugger no longer breaks at var declarations
without initialization. This is in accordance with the fact that the
interpreter does not emit bytecode for uninitialized var declarations.

Also fix the bytecode to match full-codegen's behavior wrt return
positions:
- there is a break location before the return statement, with the source
  position of the return statement.
- right before the actual return, there is another break location. The
  source position points to the end of the function.

R=rmcilroy@chromium.org, vogelheim@chromium.org
TBR=rossberg@chromium.org
BUG=v8:4690
LOG=N

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

Cr-Commit-Position: refs/heads/master@{#34388}
      d9fe836d
  33. 12 Feb, 2016 2 commits
  35. 11 Feb, 2016 1 commit
  37. 21 Jan, 2016 1 commit
  39. 18 Dec, 2015 1 commit
  41. 15 Dec, 2015 1 commit
  43. 14 Dec, 2015 2 commits
  45. 09 Dec, 2015 2 commits
  47. 04 Dec, 2015 1 commit
  49. 02 Dec, 2015 2 commits
  51. 26 Nov, 2015 1 commit
  53. 25 Nov, 2015 2 commits
  55. 19 Nov, 2015 1 commit
  57. 03 Nov, 2015 1 commit