Skip to content

V
V8
Switch branch/tag
  1. 01 Jun, 2016 2 commits
  3. 30 May, 2016 2 commits
  5. 24 May, 2016 3 commits
  7. 23 May, 2016 1 commit
  9. 19 May, 2016 1 commit
    • adamk's avatar
      Remove now-incorrect DataView accessor optimization · de7d47e2
      adamk authored 
      In ES2015, the "byteLength" and "byteOffset" properties of DataViews are
getters on the prototype, so the previously-used strategy of special-casing
them using only the receiver map is invalid.

A future CL will need to use the same strategy which will be taken for
TypedArray "length", "byteLength", and "byteOffset": adding a prototype
chain check.

BUG=v8:5018, chromium:593634

Review-Url: https://codereview.chromium.org/1984043002
Cr-Commit-Position: refs/heads/master@{#36382}
      de7d47e2
  11. 13 May, 2016 3 commits
    • cbruni's avatar
      [counters] Annotate v8 with more runtime call counters. · 407d9fce
      cbruni authored 
      By fully annotating the API with runtime counters we can properly measure
how much time we spend in total in v8. When --runtime-call-stats is specified
we now disable the fast-paths for callbacks to properly measure them.
As a drive-by-fix this CL unifies the LOG messages in api.cc.
Additionally we added missing timers to gain better resolution in the parser
and callbacks.

BUG=

Review-Url: https://codereview.chromium.org/1923893002
Cr-Commit-Position: refs/heads/master@{#36248}
      407d9fce
    • jkummerow's avatar
      [IC] Only cache handlers on a map that were compiled for that map · 8313d2f0
      jkummerow authored 
      Globally cached handler stubs shouldn't be put into the on-map caches.
This should speed up IC misses and save a bit of memory.

Drive-by fix: transitioning StoreIC handlers were erroneously never cached.

Review-Url: https://codereview.chromium.org/1974793002
Cr-Commit-Position: refs/heads/master@{#36247}
      8313d2f0
    • verwaest's avatar
      [runtime] Make sure that LookupIterator::OWN always performs a HIDDEN lookup as well. · c9a83150
      verwaest authored 
      Hidden prototypes are merely an implementation detail. Properties on an object + hidden prototype should look like properties on the object. Hence we should always perform a hidden prototype lookup. This CL removes the option to ignore hidden prototypes to avoid bugs that leak this implementation detail.

Also, the only previously valid cases were either places were we knew we didn't have a hidden prototype; or because we knew we (in the optimizing compiler) would only handle properties from the non-hidden object.The first case is already handled by directly tagging whether a receiver has a hidden prototype. In the second case we can just filter out properties from hidden prototypes.

Review-Url: https://codereview.chromium.org/1975763002
Cr-Commit-Position: refs/heads/master@{#36235}
      c9a83150
  13. 12 May, 2016 1 commit
  15. 11 May, 2016 2 commits
  17. 27 Apr, 2016 1 commit
  19. 22 Apr, 2016 1 commit
  21. 21 Apr, 2016 1 commit
  23. 20 Apr, 2016 3 commits
  25. 19 Apr, 2016 5 commits
  27. 15 Apr, 2016 1 commit
    • zhengxing.li's avatar
      X87: [ic] Use the CallFunction builtin to invoke accessors. · 96ddf420
      zhengxing.li authored 
        port 6df9a22c (r35187)

  original commit message:
  The HandlerCompiler did not properly handle the weird edge case when a
  sloppy mode function was installed as an accessor on one of the value
  wrapper prototypes and then accessed via a load from a primitive value.
  In this case we just passed the primitive value untouched instead of
  properly wrapping it first. The CallFunction builtin properly deals with
  all the funny edge cases, so we use it instead of duplicating almost all
  of the logic here (the performance difference is neglible).

BUG=

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

Cr-Commit-Position: refs/heads/master@{#35522}
      96ddf420
  29. 14 Apr, 2016 1 commit
  31. 12 Apr, 2016 3 commits
  33. 11 Apr, 2016 5 commits
  35. 06 Apr, 2016 4 commits