1. 13 Dec, 2019 1 commit
  2. 31 Oct, 2019 1 commit
  3. 22 Oct, 2019 1 commit
  4. 26 Sep, 2019 1 commit
  5. 04 Sep, 2019 1 commit
  6. 03 Sep, 2019 2 commits
  7. 30 Aug, 2019 1 commit
  8. 19 Aug, 2019 2 commits
    • Georg Neis's avatar
      [turbofan] Improve --trace-turbo-inlining and TRACE_BROKER_MISSING · 2cccb464
      Georg Neis authored
      - Eliminate unconditional heap reads in tracing code.
      - Change operator<< on ObjectRef to additionally print
        the Brief() output when the broker is disabled.
      - Print line number in TRACE_BROKER_MISSING and make
        some messages more consistent.
      - Make PrintCandidates output clearer.
      - Be more consistent about dereferencing optionals.
      
      Bug: v8:7790, chromium:990478
      Change-Id: I2917529d5138a0d63ad476d3f8fee6a963767b23
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1758311
      Commit-Queue: Georg Neis <neis@chromium.org>
      Reviewed-by: 's avatarMaya Lekova <mslekova@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#63242}
      2cccb464
    • Jakob Gruber's avatar
      [deoptimizer] More consistent semantics of height for all frame types · 9fe6b543
      Jakob Gruber authored
      Information required for deoptimization is passed from codegen to the
      deoptimizer through so-called translations. Translations contain,
      among many other things, a 'height' field. It is used during deopts to
      calculate the unoptimized frame height (but note that it does not
      correspond exactly to the frame height itself - further calculations
      on the deopt side are needed to get to the real frame height).
      
      The height field has roughly the following data flow:
      
      1. During codegen, we serialize whatever
      FrameStateDescriptor::GetHeight() returns.
      2. During deopts, serialized translations are converted into
      TranslatedFrame objects in TranslatedState::CreateNextTranslatedFrame.
      3. These are later used to arrive at the real frame height in multiple
      spots, e.g. in DoComputeInterpretedFrame and friends.
      
      Prior to this CL, we were adding and subtracting 1 in basically random
      spots. For example, for interpreted and construct stub frames we added
      1 in step 1 and subtracted 1 in step 3. For continuation frames, we
      added 1 in step 2 and subtracted it in step 3. Argument adaptor frames
      were left untouched.
      
      This CL removes all these +-1's. The height field now contains
      locals_count() for interpreted frames, and parameters_count() for
      everything else. I also tried to make the meaning of adds/subs clearer
      through use of named constants like kTheReceiver.
      
      Bug: v8:9534
      Change-Id: I6fd26886ff5aa63930f413d879d5480578d9dc7e
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1751724Reviewed-by: 's avatarSigurd Schneider <sigurds@chromium.org>
      Reviewed-by: 's avatarMichael Stanton <mvstanton@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Auto-Submit: Jakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#63238}
      9fe6b543
  9. 26 Jul, 2019 1 commit
  10. 25 Jul, 2019 1 commit
  11. 17 Jul, 2019 1 commit
  12. 08 Jul, 2019 1 commit
  13. 05 Jul, 2019 1 commit
  14. 13 Jun, 2019 1 commit
  15. 23 May, 2019 2 commits
  16. 22 May, 2019 2 commits
  17. 21 May, 2019 1 commit
  18. 14 May, 2019 1 commit
  19. 10 May, 2019 1 commit
  20. 09 May, 2019 2 commits
  21. 07 May, 2019 1 commit
  22. 06 May, 2019 1 commit
  23. 29 Apr, 2019 3 commits
  24. 18 Apr, 2019 1 commit
  25. 08 Apr, 2019 1 commit
  26. 14 Mar, 2019 1 commit
  27. 12 Mar, 2019 1 commit
  28. 06 Mar, 2019 1 commit
    • Georg Neis's avatar
      [turbofan] Don't access heap in ReduceElementAccess · 4d39e342
      Georg Neis authored
      This CL builds on top of feedback preprocessing. It brokerizes
      all parts of element access reduction and disallows heap access there
      (except for debug tracing).
      
      To make this work without breaking tests (when concurrent inlining is
      enabled):
      - We don't inline functions that weren't serialized for compilation.
      - We don't optimize for constant typed-array receivers when the typed
        array wasn't serialized.
      
      This means that from now on --concurrent-inlining (and thus --future)
      may result in less optimization than the default configuration.
      
      Bug: v8:7790
      Change-Id: I22685258b7d841fc9183bf99775d3f09cd272927
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1495556
      Commit-Queue: Georg Neis <neis@chromium.org>
      Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarMaya Lekova <mslekova@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#60061}
      4d39e342
  29. 19 Feb, 2019 1 commit
  30. 13 Feb, 2019 2 commits
  31. 22 Jan, 2019 1 commit
  32. 17 Jan, 2019 1 commit