Skip to content

V
V8
Switch branch/tag
  1. 20 Apr, 2017 2 commits
  3. 13 Apr, 2017 1 commit
  5. 11 Apr, 2017 1 commit
    • gsathya's avatar
      [ESNext] Implement DynamicImportCall · 94283dcf
      gsathya authored 
      This patch implements the runtime semantics of dynamic import.

We create a new ASTNode so that we can pass the JSFunction closure() to
the runtime function from which we get the script_url.

d8 implements the embedder logic required to load and evaluate the modules.

The API is mostly implemented as specified.

BUG=8:5785

Review-Url: https://codereview.chromium.org/2703563002
Cr-Commit-Position: refs/heads/master@{#44551}
      94283dcf
  7. 28 Mar, 2017 1 commit
  9. 24 Mar, 2017 2 commits
  11. 22 Mar, 2017 1 commit
  13. 21 Mar, 2017 2 commits
  15. 15 Mar, 2017 2 commits
  17. 14 Mar, 2017 1 commit
  19. 28 Feb, 2017 1 commit
  21. 23 Feb, 2017 1 commit
  23. 22 Feb, 2017 1 commit
  25. 21 Feb, 2017 1 commit
  27. 17 Feb, 2017 1 commit
  29. 14 Feb, 2017 1 commit
  31. 13 Feb, 2017 6 commits
  33. 12 Feb, 2017 1 commit
  35. 07 Feb, 2017 5 commits
  37. 06 Feb, 2017 2 commits
    • mvstanton's avatar
      [TypeFeedbackVector] Root feedback vectors at function literal site. · aea3ce3d
      mvstanton authored 
      TypeFeedbackVectors are strongly rooted by a closure. However, in modern
JavaScript closures are created and abandoned more freely. An important
closure may not be present in the root-set at time of garbage collection,
even though we've cached optimized code and use it regularly. For
example, consider leaf functions in an event dispatching system. They may
well be "hot," but tragically non-present when we collect the heap.

Until now, we've relied on a weak root to cache the feedback vector in
this case. Since there is no way to signal intent or relative importance,
this weak root is as susceptible to clearing as any other weak root at
garbage collection time.

Meanwhile, the feedback vector has become more important. All of our
ICs store their data there. Literal and regex boilerplates are stored there.
If we lose the vector, then we not only lose optimized code built from
it, we also lose the very feedback which allowed us to create that optimized
code. Therefore it's vital to express that dependency through the root
set.

This CL does this by creating a strong link to a feedback
vector at the instantiation site of the function closure.
This instantiation site is in the code and feedback vector
of the outer closure.

BUG=v8:5456

Review-Url: https://codereview.chromium.org/2674593003
Cr-Commit-Position: refs/heads/master@{#42953}
      aea3ce3d
    • ishell's avatar
      [ic] Encode [Keyed]StoreIC's language mode in slot kind instead of code object's flags. · 52555c86
      ishell authored 
      BUG=v8:5917

Review-Url: https://codereview.chromium.org/2676583002
Cr-Commit-Position: refs/heads/master@{#42949}
      52555c86
  39. 04 Feb, 2017 1 commit
  41. 02 Feb, 2017 4 commits
  43. 30 Jan, 2017 2 commits
    • bjaideep's avatar
      PPC/s390: [TypeFeedbackVector] Combine the literals array and the feedback vector. · 626b95e3
      bjaideep authored 
      Port 93f05b64

Original Commit Message:

    They have the same lifetime. It's a match!

    Both structures are native context dependent and dealt with (creation,
    clearing, gathering feedback) at the same time. By treating the spaces used
    for literal boilerplates as feedback vector slots, we no longer have to keep
    track of the materialized literal count elsewhere.

    A follow-on CL removes even more parser infrastructure related to this count.

R=mvstanton@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=v8:5456
LOG=N

Review-Url: https://codereview.chromium.org/2659413002
Cr-Commit-Position: refs/heads/master@{#42778}
      626b95e3
    • mvstanton's avatar
      [TypeFeedbackVector] Combine the literals array and the feedback vector. · 93f05b64
      mvstanton authored 
      They have the same lifetime. It's a match!

Both structures are native context dependent and dealt with (creation,
clearing, gathering feedback) at the same time. By treating the spaces used
for literal boilerplates as feedback vector slots, we no longer have to keep
track of the materialized literal count elsewhere.

A follow-on CL removes even more parser infrastructure related to this count.

BUG=v8:5456

Review-Url: https://codereview.chromium.org/2655853010
Cr-Commit-Position: refs/heads/master@{#42771}
      93f05b64