1. 19 Jan, 2017 1 commit
  2. 13 Jan, 2017 4 commits
  3. 12 Jan, 2017 1 commit
  4. 02 Dec, 2016 1 commit
  5. 29 Nov, 2016 1 commit
  6. 28 Nov, 2016 1 commit
  7. 15 Nov, 2016 2 commits
  8. 11 Nov, 2016 1 commit
    • verwaest's avatar
      Make private symbols non-enumerable · 135b9f93
      verwaest authored
      Methods in the runtime that enumerate over properties should never deal with private symbols. Most commonly such methods only loop over enumerable properties. This fix avoids accidentally handling private symbols in methods that only deal with enumerable properties. Methods that need to look at non-enumerable properties as well still have to manually filter private symbols (e.g., the KeyAccumulator).
      
      BUG=chromium:664411
      
      Review-Url: https://codereview.chromium.org/2499593002
      Cr-Commit-Position: refs/heads/master@{#40932}
      135b9f93
  9. 04 Nov, 2016 1 commit
    • vogelheim's avatar
      V8 support for cached accessors. · cadcd787
      vogelheim authored
      Some accessors requires little to no computation at all, its result can be
      cached in a private property, avoiding the call overhead.
      Calls to the getter are translated into a cheap property load.
      
      Follow-on to crrev.com/2347523003, from peterssen@google.com
      
      BUG=chromium:634276, v8:5548
      
      Review-Url: https://codereview.chromium.org/2405213002
      Cr-Commit-Position: refs/heads/master@{#40765}
      cadcd787
  10. 31 Oct, 2016 1 commit
  11. 24 Oct, 2016 1 commit
  12. 21 Oct, 2016 4 commits
  13. 06 Sep, 2016 1 commit
  14. 05 Sep, 2016 2 commits
    • mlippautz's avatar
      KeyLookupCache,DescriptorLookupCache: heap.h -> lookup.h · 7f53dac6
      mlippautz authored
      R=ulan@chromium.org
      
      Review-Url: https://codereview.chromium.org/2311003002
      Cr-Commit-Position: refs/heads/master@{#39185}
      7f53dac6
    • fmeawad's avatar
      [RuntimeCallStats] Move tracing runtime instrumentation closer to the original version. · e5ba156d
      fmeawad authored
      After we landed the tracing runtime call stats, which gave
      us a lot of V8 insight in tracing, we noticed that there is
      some arising issues and discrepancies.
      
      Issues include:
      Missing trace events, that happened due to
      transforming those trace events into runtime calls
      
      Discrepancies include:
      Missing categories in Runtime call stats like GC,
      because we are not handling the Scoped runtime calls
      properly in the tracing version.
      
      To reduce/eliminate those issue, we are taking a small
      step back. We are unifying the RuntimeStats code and
      using the original one. That would allow us to use all
      the original probes but emit trace events from them.
      We are also putting back the trace-events in their place.
      
      The output from both system should be intact (Except of
      the addition of the missing trace-events).
      
      Also as a byproduct, we are reducing the number of context
      scopes by half since we are using the same scope as
      runtime call stats.
      
      As a follow up to this CL, we will address the non-scoped
      Runtime Call Stats (mainly in GC).
      BUG=642373
      
      Review-Url: https://codereview.chromium.org/2296243002
      Cr-Commit-Position: refs/heads/master@{#39180}
      e5ba156d
  15. 10 Aug, 2016 1 commit
  16. 08 Aug, 2016 1 commit
  17. 05 Aug, 2016 1 commit
  18. 03 Aug, 2016 4 commits
  19. 11 Jul, 2016 1 commit
  20. 07 Jul, 2016 1 commit
    • ishell's avatar
      [runtime] Better encapsulation of dictionary objects handling in lookup iterator. · 3fbb4521
      ishell authored
      Now LookupIterator follows the same pattern of prepare transition, apply transition
      and write value when adding new properties to dictionary objects.
      
      JSGlobalObject case:
      * Prepare transition phase ensures that there is a "transition" property cell
        prepared for receiving a value.
      * Apply transition phase does nothing.
      * Prepare for data property phase ensures that the existing property cell can
        receive the value.
      * Write value phase writes value directly to the current property cell.
      
      JSObject case:
      * Prepare transition phase prepares the object for receiving a data value (which
        could switch an object to dictionary mode).
      * Apply transition phase migrates object to a transition map. If the map happened
        to be a dictionary mode object's map then an uninitialized entry added to the
        properties dictionary.
      * Prepare for data property phase does nothing.
      * Write value phase just puts value to the properties dictionary.
      
      BUG=chromium:576312
      
      Review-Url: https://codereview.chromium.org/2127583002
      Cr-Commit-Position: refs/heads/master@{#37585}
      3fbb4521
  21. 27 Jun, 2016 1 commit
  22. 15 Jun, 2016 1 commit
  23. 14 Jun, 2016 2 commits
  24. 13 Jun, 2016 3 commits
  25. 12 Jun, 2016 1 commit
  26. 08 Jun, 2016 1 commit
    • jkummerow's avatar
      Keep prototype maps in dictionary mode until ICs see them · be0494ba
      jkummerow authored
      Adding properties to prototypes is faster when we don't force their
      maps into fast mode yet. Once a prototype shows up in the IC system,
      its setup phase is likely over, and it makes sense to transition it
      to fast properties.
      This patch speeds up the microbenchmark in the bug by 20x.
      Octane-Typescript sees a 3% improvement.
      
      BUG=chromium:607010
      
      Review-Url: https://codereview.chromium.org/2036493006
      Cr-Commit-Position: refs/heads/master@{#36828}
      be0494ba