1. 28 Dec, 2015 1 commit
  2. 17 Dec, 2015 3 commits
  3. 16 Dec, 2015 1 commit
  4. 15 Dec, 2015 3 commits
  5. 12 Dec, 2015 1 commit
  6. 11 Dec, 2015 1 commit
  7. 10 Dec, 2015 5 commits
  8. 03 Dec, 2015 1 commit
  9. 02 Dec, 2015 3 commits
    • littledan's avatar
      Revert of Disable non-standard Promise functions in staging (patchset #1 id:1... · c6323632
      littledan authored
      Revert of Disable non-standard Promise functions in staging (patchset #1 id:1 of https://codereview.chromium.org/1478533002/ )
      
      Reason for revert:
      Will test better; there seems to be a bug related to this.
      
      Original issue's description:
      > Reland of Disable non-standard Promise functions in staging (patchset #1 id:1 of https://codereview.chromium.org/1473603002/ )
      >
      > Reason for revert:
      > Breakage in Ignition seems unrelated; relanding.
      >
      > Original issue's description:
      > > Revert of Disable non-standard Promise functions in staging (patchset #5 id:80001 of https://codereview.chromium.org/1469543003/ )
      > >
      > > Reason for revert:
      > > [Sheriff] This breaks ignition on arm sim debug:
      > > https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm%20-%20sim%20-%20debug/builds/5317
      > >
      > > Seems to not be caught by the cq bot that builds release with dchecks.
      > >
      > > Original issue's description:
      > > > Disable non-standard Promise functions in staging
      > > >
      > > > This patch removes Promise functions and methods which are absent
      > > > from the ES2015 specification when the --es-staging flag is on.
      > > >
      > > > BUG=v8:3237
      > > > R=rossberg
      > > > LOG=Y
      > > >
      > > > Committed: https://crrev.com/941251af7e04d50ac2243da2870249a42111221a
      > > > Cr-Commit-Position: refs/heads/master@{#32194}
      > >
      > > TBR=rossberg@chromium.org,littledan@chromium.org
      > > NOPRESUBMIT=true
      > > NOTREECHECKS=true
      > > NOTRY=true
      > > BUG=v8:3237
      > >
      > > Committed: https://crrev.com/86bd2b3c23b562213d5af158849dcd65f347a827
      > > Cr-Commit-Position: refs/heads/master@{#32199}
      >
      > TBR=rossberg@chromium.org,rmcilroy@chromium.org,machenbach@chromium.org
      > NOPRESUBMIT=true
      > NOTREECHECKS=true
      > NOTRY=true
      > BUG=v8:3237
      >
      > Committed: https://crrev.com/9278b7b05a45c2089007e8b61822af96b5d0c8df
      > Cr-Commit-Position: refs/heads/master@{#32235}
      
      TBR=rossberg@chromium.org,rmcilroy@chromium.org,machenbach@chromium.org
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=v8:3237
      
      Review URL: https://codereview.chromium.org/1493713004
      
      Cr-Commit-Position: refs/heads/master@{#32530}
      c6323632
    • danno's avatar
      [stubs] A new approach to TF stubs · 3e7e3ed7
      danno authored
      * Add a sibling interface to InterpreterAssembler called
        CodeStubAssembler which provides a wrapper around the
        RawMachineAssembler and is intented to make it easy to build
        efficient cross-platform code stubs. Much of the implementation
        of CodeStubAssembler is shamelessly stolen from the
        InterpreterAssembler, and the idea is to eventually merge the
        two interfaces somehow, probably moving the
        InterpreterAssembler interface over to use the
        CodeStubAssembler. Short-term, however, the two interfaces
        shall remain decoupled to increase our velocity developing the
        two systems in parallel.
      * Implement the StringLength stub in TurboFan with the new
        CodeStubAssembler. Replace and remove the old Hydrogen-stub
        version.
      * Remove a whole slew of machinery to support JavaScript-style
        code stub generation, since it ultimately proved unwieldy,
        brittle and baroque. This cleanup includes removing the shared
        code stub context, several example stubs and a tangle of build
        file changes.
      
      BUG=v8:4587
      LOG=n
      
      Review URL: https://codereview.chromium.org/1475953002
      
      Cr-Commit-Position: refs/heads/master@{#32508}
      3e7e3ed7
    • sigurds's avatar
      [turbofan] Initial support for escape analysis. · aa0ddf7d
      sigurds authored
      This is the first part of escape analysis for turbofan.
      At the moment, there is no deopt support, and support
      for loops is partial (only binary Phis are handled).
      
      The CL includes 4 unittests.
      
      There are also 8 new mjsunit tests, some of which are
      skiped as they require features not yet implemented.
      
      BUG=v8:4586
      LOG=n
      
      Review URL: https://codereview.chromium.org/1457683003
      
      Cr-Commit-Position: refs/heads/master@{#32498}
      aa0ddf7d
  10. 01 Dec, 2015 1 commit
  11. 26 Nov, 2015 3 commits
  12. 25 Nov, 2015 2 commits
  13. 24 Nov, 2015 3 commits
  14. 13 Nov, 2015 2 commits
    • ishell's avatar
      Object's body descriptors refactoring. · 138eb324
      ishell authored
      1) Body descriptors moved to their own header files.
      2) Missing body descriptors added.
      3) Template versions of HeapObject::Iterate*() methods added.
      4) Body descriptors support new kind of queries: IsValidSlot(offset) which can be used for invalid slots filtering.
      
      This is a first step towards virtual and static visitors unification and support in-object properties in built-in (sub-)classes.
      
      Review URL: https://codereview.chromium.org/1440243002
      
      Cr-Commit-Position: refs/heads/master@{#31980}
      138eb324
    • bmeurer's avatar
      [turbofan] Introduce JSCallReducer to strength reduce JSCallFunction nodes. · 55c07a8b
      bmeurer authored
      The JSCallReducer runs together with inlining and tries to strength
      reduce JSCallFunction nodes; currently it can fold
      Function.prototype.call and Function.prototype.apply (with arguments),
      and make it possible to inline across them.
      
      In the case of Function.prototype.apply with arguments we still have to
      leave the JSCreateArguments node in the graph because there might be
      other (frame state) uses. Once escape analysis is ready, it will take
      care of removing these nodes and adding appropriate transitions for the
      deoptimizer.
      
      R=jarin@chromium.org
      BUG=v8:4551
      LOG=n
      
      Review URL: https://codereview.chromium.org/1445513002
      
      Cr-Commit-Position: refs/heads/master@{#31979}
      55c07a8b
  15. 11 Nov, 2015 1 commit
  16. 09 Nov, 2015 1 commit
    • fedor's avatar
      binary-operator-reducer: reduce mul+div(shift) · 461e5b49
      fedor authored
      Reduction Input:
      
          ChangeInt32ToFloat64=>          TruncateFloat64ToInt32
                               Float64Mul=>
          ChangeInt32ToFloat64=>          Float64Div=>TruncateFloat64ToInt32
      
      Output:
      
               =>  TruncateInt64ToInt32
      Int64Mul
               =>  Int64Shr => TruncateInt64ToInt32
      
      Test code:
      
          function mul(a, b) {
            var l = a & 0x3ffffff;
            var h = b & 0x3ffffff;
            var m = l * h;
      
            var rl = m & 0x3ffffff;
            var rh = (m / 0x4000000) | 0;
      
            return rl | rh;
          }
      
          mul(1, 2);
          var a0 = mul(0x3ffffff, 0x3ffffff);
          mul(0x0, 0x0);
          %OptimizeFunctionOnNextCall(mul);
          var a1 = mul(0x3ffffff, 0x3ffffff);
      
          print(a0 + ' == ' + a1);
      
      BUG=
      R=mstarzinger@chromium.org
      
      Review URL: https://codereview.chromium.org/1350223006
      
      Cr-Commit-Position: refs/heads/master@{#31899}
      461e5b49
  17. 08 Nov, 2015 1 commit
  18. 05 Nov, 2015 1 commit
  19. 04 Nov, 2015 2 commits
  20. 03 Nov, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Split JSGlobalObjectSpecialization into separate class. · 4eb41ba7
      bmeurer authored
      The JSNativeContextSpecialization class is getting rather huge with all
      the stuff related to property and element access going in. Splitting off
      the global object related stuff into JSGlobalObjectSpecialization seems
      like a natural separation, especially since the global object
      specialization is sort of separate issue anyway.  This is neutral
      functionality- and performance-wise.
      
      R=jarin@chromium.org
      BUG=v8:4470
      LOG=n
      
      Review URL: https://codereview.chromium.org/1417043006
      
      Cr-Commit-Position: refs/heads/master@{#31748}
      4eb41ba7
  21. 02 Nov, 2015 2 commits
  22. 30 Oct, 2015 1 commit