1. 22 Feb, 2017 1 commit
  2. 21 Feb, 2017 1 commit
    • bjaideep's avatar
      PPC/s390: [everywhere] Custom representation for frame type · af76645b
      bjaideep authored
      Port fd596007
      
      Original Commit Message:
      
          Use an opaque format for the frame type marker on the stack, where the
          marker is simply shifted left by 1 instead of being a Smi. This allows
          us to generate simpler code for frame initialisation, as we can push a
          smaller value, decreasing the prologue by 4 bytes and one instruction.
      
      R=leszeks@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2709483007
      Cr-Commit-Position: refs/heads/master@{#43356}
      af76645b
  3. 09 Feb, 2017 1 commit
  4. 08 Feb, 2017 1 commit
  5. 07 Feb, 2017 1 commit
  6. 06 Feb, 2017 2 commits
    • bjaideep's avatar
      Revert of PPC/s390: [debugger] remove debugger statement support from FCG/CS.... · 8330952b
      bjaideep authored
      Revert of PPC/s390: [debugger] remove debugger statement support from FCG/CS. (patchset #1 id:1 of https://codereview.chromium.org/2672813002/ )
      
      Reason for revert:
      Original CL got reverted https://codereview.chromium.org/2672823007
      
      Original issue's description:
      > PPC/s390: [debugger] remove debugger statement support from FCG/CS.
      >
      > Port eef855a1
      >
      > R=yangguo@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      > BUG=
      > LOG=N
      >
      > Review-Url: https://codereview.chromium.org/2672813002
      > Cr-Commit-Position: refs/heads/master@{#42898}
      > Committed: https://chromium.googlesource.com/v8/v8/+/f2d2ebcae8f31a7787778c429018156a432662e2
      
      TBR=joransiu@ca.ibm.com,jyan@ca.ibm.com,michael_dawson@ca.ibm.com,yangguo@chromium.org
      # Not skipping CQ checks because original CL landed more than 1 days ago.
      BUG=
      
      Review-Url: https://codereview.chromium.org/2677183003
      Cr-Commit-Position: refs/heads/master@{#42972}
      8330952b
    • 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
  7. 02 Feb, 2017 1 commit
  8. 30 Jan, 2017 2 commits
  9. 27 Jan, 2017 1 commit
    • bjaideep's avatar
      PPC/s390: [liveedit] reimplement frame restarting. · 9515f7ed
      bjaideep authored
      Port 3f47c63d
      
      Original Commit Message:
      
          Previously, when restarting a frame, we would rewrite all frames
          between the debugger activation and the frame to restart to squash
          them, and replace the return address with that of a builtin to
          leave that rewritten frame, and restart the function by calling it.
      
          We now simply remember the frame to drop to, and upon returning
          from the debugger, we check whether to drop the frame, load the
          new FP, and restart the function.
      
      R=yangguo@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=v8:5587
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2663453004
      Cr-Commit-Position: refs/heads/master@{#42748}
      9515f7ed
  10. 12 Jan, 2017 1 commit
  11. 19 Dec, 2016 1 commit
  12. 22 Nov, 2016 1 commit
  13. 31 Oct, 2016 1 commit
  14. 27 Oct, 2016 1 commit
    • ishell's avatar
      [ic] Remove unnecessary access rights checks from the IC handlers. · 8ba4af44
      ishell authored
      The reasons are:
      1) Type feedback vectors are not shared between different native contexts and
         therefore the IC handler created for one native context will not be reused
         in other native context.
      2) Access rights revocation is not supported at all, therefore given (1) once
         we pass the access check we don't have to check access rights again.
      
      BUG=v8:5561
      
      Review-Url: https://codereview.chromium.org/2455953002
      Cr-Commit-Position: refs/heads/master@{#40627}
      8ba4af44
  15. 20 Oct, 2016 1 commit
  16. 18 Oct, 2016 1 commit
  17. 17 Oct, 2016 1 commit
  18. 07 Oct, 2016 3 commits
  19. 06 Sep, 2016 1 commit
    • mlippautz's avatar
      Move kMaxRegularHeapObjectSize into globals · 059b5643
      mlippautz authored
      This way we avoid the cyclic dependency between objects.h and heap.h and still
      have one definition. Add a static assert that this size is indeed smaller than
      the payload of a page.
      
      Follow ups can finally remove the dependency on spaces.h for all heap.h users.
      
      R=ulan@chromium.org,bmeurer@chromium.org,vogelheim@chromium.og
      
      Review-Url: https://codereview.chromium.org/2311203002
      Cr-Commit-Position: refs/heads/master@{#39206}
      059b5643
  20. 31 Aug, 2016 1 commit
  21. 18 Aug, 2016 1 commit
  22. 19 Jul, 2016 1 commit
    • bjaideep's avatar
      PPC/s390: [builtins] Introduce a builtin for Abort(). · a660062d
      bjaideep authored
      Port 9be015a2
      
      Original commit message:
      
          Calling Runtime::kAbort through a builtin instead of the c-entry stub
          will allow to generate the call in a background thread, because a
          builtin provides its own handle, whereas a code stub does not.
      
      R=ahaas@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com
      
      BUG=
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2166553002
      Cr-Commit-Position: refs/heads/master@{#37877}
      a660062d
  23. 11 Jul, 2016 1 commit
  24. 30 Jun, 2016 1 commit
    • bjaideep's avatar
      PPC/s390: [builtins] New frame type for exits to C++ builtins · 3ee6b808
      bjaideep authored
      Port 5febc27b
      
      Original commit message:
      
          Prior to this commit, calls to C++ builtins created standard exit
          frames, which are skipped when constructing JS stack traces. In order to
          show these calls on traces, we introduce a new builtin exit frame type.
      
          Builtin exit frames contain target and new.target on the stack and are
          not skipped during stack trace construction.
      
      R=jgruber@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com
      
      BUG=v8:4815
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2105023008
      Cr-Commit-Position: refs/heads/master@{#37461}
      3ee6b808
  25. 28 Jun, 2016 1 commit
    • bjaideep's avatar
      PPC/s390: Reland [heap] Avoid the use of cells to point from code to new-space objects. · 85cebe73
      bjaideep authored
      Port 5e058540
      
      Original commit message:
      
          The reason for reverting is: This breaks gc-stress bot:
          https://chromegw.corp.google.com/i/client.v8/builders/V8%20Linux64%20GC%20Stress%20-%20custom%20snapshot
      
          Abortion of compaction could cause duplicate entries in the typed-old-to-new remembered set.
          These duplicates could cause a DCHECK to trigger which checks that slots recorded in the
          remembered set never point to to-space. This reland-CL allows duplicates in the remembered
          set by removing the DCHECK, and additionally clears entries in the remembered set if objects are moved.
      
          Original issue's description:
      
          Cells were needed originally because there was no typed remembered set to
          record direct pointers from code space to new space. A previous
          CL (https://codereview.chromium.org/2003553002/) already introduced
          the remembered set, this CL uses it.
      
          This CL
          * stores direct pointers in code objects, even if the target is in new space,
          * records the slot of the pointer in typed-old-to-new remembered set,
          * adds a list which stores weak code-to-new-space references,
          * adds a test to test-heap.cc for weak code-to-new-space references,
          * removes prints in tail-call-megatest.js
      
      R=ahaas@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com
      
      BUG=
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2108673003
      Cr-Commit-Position: refs/heads/master@{#37346}
      85cebe73
  26. 27 Jun, 2016 1 commit
  27. 20 Jun, 2016 1 commit
  28. 16 Jun, 2016 1 commit
  29. 15 Jun, 2016 1 commit
  30. 27 May, 2016 1 commit
  31. 11 May, 2016 1 commit
    • bjaideep's avatar
      PPC: [crankshaft] Fragmentation-free allocation folding. · ce7d7761
      bjaideep authored
      Port 61f5fbbb
      
      Original commit message:
      
            The new allocation folding implementation avoids fragmentation between folded allocation.
            As a consequence, our heap will always be iterable i.e. we do not have to perform a
            garbage collection before iterating the heap.
      
      R=hpayer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com
      
      BUG=chromium:580959
      LOG=N
      
      Review-Url: https://codereview.chromium.org/1970633002
      Cr-Commit-Position: refs/heads/master@{#36184}
      ce7d7761
  32. 09 May, 2016 1 commit
  33. 04 May, 2016 1 commit
  34. 27 Apr, 2016 1 commit
  35. 06 Apr, 2016 1 commit
    • mbrandy's avatar
      PPC: [generators] Decouple generator resume from fullcodegen. · 1e001e71
      mbrandy authored
      Port 974721c6
      
      Original commit message:
          Introduce a ResumeGeneratorTrampoline, which does the actual stack state
          reconstruction (currently always restores a fullcodegen frame), and
          introduce appropriate TurboFan builtins for %GeneratorPrototype%.next,
          %GeneratorPrototype%.return and %GeneratorPrototype%.throw based on
          this native builtin.
      
          Also unify the flooding in case of step-in to always work based on
          JSFunction and remove the special casing for JSGeneratorObject.
      
      R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, bjaideep@ca.ibm.com
      BUG=chromium:513471
      LOG=n
      
      Review URL: https://codereview.chromium.org/1868683002
      
      Cr-Commit-Position: refs/heads/master@{#35314}
      1e001e71
  36. 01 Apr, 2016 1 commit