1. 20 Feb, 2017 1 commit
  2. 09 Feb, 2017 1 commit
  3. 07 Feb, 2017 1 commit
  4. 06 Feb, 2017 1 commit
  5. 12 Jan, 2017 1 commit
  6. 10 Jan, 2017 1 commit
  7. 22 Nov, 2016 1 commit
  8. 08 Nov, 2016 1 commit
  9. 31 Oct, 2016 1 commit
  10. 27 Oct, 2016 2 commits
  11. 17 Oct, 2016 2 commits
  12. 06 Oct, 2016 1 commit
  13. 23 Sep, 2016 1 commit
  14. 22 Sep, 2016 1 commit
  15. 20 Sep, 2016 1 commit
  16. 16 Sep, 2016 1 commit
    • ishell's avatar
      [stubs] Port StoreTransitionStub and ElementsTransitionAndStoreStub to TurboFan. · 130d9893
      ishell authored
      This CL also cleans up related interface descriptors:
      1) unused StoreTransitionDescriptor is removed and VectorStoreTransitionDescriptor is
      renamed to StoreTransitionDescriptor.
      2) on ia32/x87 architectures slot and vector are passed on the stack (dispatcher/handlers
      cleanup will be addressed in a separate CL).
      
      These two stub ports have to be combined in one CL because:
      1) without changing the StoreTransitionDescriptor TF was not able to compile them
      on ia32/x87 (because of lack of registers),
      2) it was not possible to change the descriptor first because Crankshaft was not able
      to deal with the stack allocated parameters in case of a stub failure.
      
      TBR=jkummerow@chromium.org
      BUG=v8:5269
      
      Review-Url: https://codereview.chromium.org/2313093002
      Cr-Commit-Position: refs/heads/master@{#39476}
      130d9893
  17. 15 Sep, 2016 1 commit
  18. 21 Jul, 2016 1 commit
  19. 20 Jul, 2016 1 commit
    • ishell's avatar
      [ic] Fix megamorphic stub cache probing on some platforms. · 7da34f8a
      ishell authored
      This CL fixes weird performance implications when changing layout of Code::flags field:
      it happened that the unused ICStateField with MONOMORPHIC value in the handlers' flags
      was accidentally offsetting the underflow bug in stub cache probing code on arm, arm64,
      mips and mips64.
      
      Stub cache tests now work even when snapshot is enabled.
      
      Drive-by-change: Fixed counters manipulation on arm64 and mips64.
      
      BUG=chromium:618701
      
      Review-Url: https://codereview.chromium.org/2161153002
      Cr-Commit-Position: refs/heads/master@{#37910}
      7da34f8a
  20. 15 Jul, 2016 1 commit
  21. 14 Jul, 2016 2 commits
  22. 13 Jul, 2016 2 commits
  23. 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
  24. 14 Jun, 2016 1 commit
  25. 13 Jun, 2016 1 commit
    • jkummerow's avatar
      [--runtime-call-stats] Fix ACCESSOR handler computation · 31ca317a
      jkummerow authored
      When running with FLAG_runtime_call_stats, native accessor accesses must
      go through the runtime for accurate accounting. Previously the slow_stub()
      was used as a handler in order to accomplish this, but it could never be
      looked up from the code cache successfully due to mismatched code flags,
      which could cause more handler recompilations than in normal operation.
      This patch fixes that by emitting a runtime call into the compiled
      handler instead of using the slow_stub().
      
      Drive-by cleanup: drop the unused StoreIC_Megamorphic builtin.
      
      Review-Url: https://codereview.chromium.org/2054133002
      Cr-Commit-Position: refs/heads/master@{#36926}
      31ca317a
  26. 06 Jun, 2016 1 commit
  27. 24 May, 2016 1 commit
  28. 23 May, 2016 1 commit
  29. 22 Apr, 2016 1 commit
  30. 20 Apr, 2016 2 commits
  31. 19 Apr, 2016 1 commit
  32. 14 Apr, 2016 1 commit
  33. 06 Apr, 2016 1 commit
    • verwaest's avatar
      Use a dictionary-mode code cache on the map rather than a dual system. · d2eb555e
      verwaest authored
      The previous code cache system required stubs to be marked with a StubType, causing them to be inserted either into a fixed array or into a dictionary-mode code cache. This could cause names to be in both cases, and lookup would just find the "fast" one first. Given that we clear out the caches on each GC, the memory overhead shouldn't be too bad. Additionally, the dictionary itself should just stay linear for small arrays; that's faster anyway.
      
      This CL additionally deletes some dead IC code.
      
      BUG=
      
      Review URL: https://codereview.chromium.org/1846963002
      
      Cr-Commit-Position: refs/heads/master@{#35291}
      d2eb555e
  34. 01 Apr, 2016 1 commit
    • bmeurer's avatar
      [ic] Use the CallFunction builtin to invoke accessors. · 6df9a22c
      bmeurer authored
      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).
      
      R=verwaest@chromium.org
      BUG=chromium:599073, v8:4413
      LOG=n
      
      Review URL: https://codereview.chromium.org/1845243005
      
      Cr-Commit-Position: refs/heads/master@{#35187}
      6df9a22c
  35. 21 Mar, 2016 1 commit