Skip to content

V
V8
Switch branch/tag
  1. 26 Sep, 2016 26 commits
  3. 24 Sep, 2016 10 commits
  5. 23 Sep, 2016 4 commits
    • dpranke's avatar
      Change git_url var to chromium_url in DEPS. · faa1ebb3
      dpranke authored 
      This makes the variable name for the repo consistent w/ chromium,
so that we can use a single variable across repos.

R=machenbach@chromium.org

Review-Url: https://codereview.chromium.org/2362973002
Cr-Commit-Position: refs/heads/master@{#39698}
      faa1ebb3
    • littledan's avatar
      Ship async functions · 9f7540a0
      littledan authored 
      Intent to ship discussion:
https://groups.google.com/forum/#!topic/v8-users/gwpcEIrgIZY

BUG=v8:4483

Review-Url: https://codereview.chromium.org/2356943002
Cr-Commit-Position: refs/heads/master@{#39697}
      9f7540a0
    • adamk's avatar
      [modules] Initialize requested_modules before recursing in Module::Instantiate · 756f6690
      adamk authored 
      Also fix recursive call to avoid going back through the API.

R=neis@chromium.org
BUG=v8:1569

Review-Url: https://codereview.chromium.org/2366063002
Cr-Commit-Position: refs/heads/master@{#39696}
      756f6690
    • littledan's avatar
      Improve stack traces for async functions · f296dad9
      littledan authored 
      This patch tracks the stack of async functions differently from other
Promise async stack tracking. With this patch, the stack trace of a
callstack of async functions should look similarly to the call stack
if all of the functions were synchronous. An example can be found in
the updated test expectations: https://codereview.chromium.org/2362923002 .

The new stack traces are implemented using existing mechanisms in the
inspector. The inspector has two ways to save async stack traces: recurring
and non-recurring stacks. An example of a non-recurring stack is setTimeout,
and a recurring one is saved for setInterval. Recurring stacks are deleted
only when a special "cancel" function is called, rather than being deleted
after being used the first time. Previous Promise async stack tracking always
used non-recurring stacks.

For async functions, this patch saves a recurring stack. The top frame of
the stack is duplicated, as the resuming function contains a similar frame;
the devtools frontend is responsible for removing or marking this frame,
which it can do based on seeing the [async function] line which follows it.
The second frame will instead be provided by the resuming execution
context. The recurring stack is saved when the async function is entered, and
it is deleted from a finally block. The id of the stack is saved in the outer
Promise being constructed by the async function. When an intermediate
throwaway Promise will be triggered as a reaction, it will be identified as
such based on its debugging metadata, and the corresponding async function's
recurring stack will be used.

BUG=v8:4483

Review-Url: https://codereview.chromium.org/2357423002
Cr-Commit-Position: refs/heads/master@{#39695}
      f296dad9