1. 10 Jun, 2020 1 commit
  2. 08 Jun, 2020 2 commits
  3. 02 Jun, 2020 1 commit
  4. 26 May, 2020 1 commit
  5. 21 Aug, 2019 1 commit
  6. 21 May, 2019 1 commit
  7. 01 Apr, 2019 1 commit
  8. 21 Jun, 2018 1 commit
  9. 19 Oct, 2017 1 commit
    • Mike Stanton's avatar
      [Turbofan] Model JSToBoolean as a simplified operator · 78fc6668
      Mike Stanton authored
      Because the toboolean operator may lower to a builtin call (which is
      effectful in turbofan parlance after effect control linearization),
      it really should be encoded as a simplified operator, which can
      be optimized with respect for the effect chain in linearization.
      
      No new functionality here, rather a furniture rearrangement in
      the TurboFan node structure.
      
      Bug: v8:6929
      Change-Id: I371fd22941397d5c28d13bded2738161d8da8275
      Reviewed-on: https://chromium-review.googlesource.com/725721Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Michael Stanton <mvstanton@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48727}
      78fc6668
  10. 11 Jul, 2017 1 commit
    • Alexandre Talon's avatar
      [Turbofan] Enable reducers to report their name to make reducer tracing clearer · 7a75da34
      Alexandre Talon authored
      Each reducer now has a virtual reducer_name function, returning its name
      (the name of the class containing this reducer). This gets displayed when
      using the --trace_turbo_reduction flag. Also when using this flags more
      messages are displayed.
      
      Actually when a node is replaced in-place (which is called an update
      of the node), other reducers can still update it right after the
      in-place replacement. When a node is really replaced (not in-place),
      then we stop trying to apply reducers to it before we propagate the
      reduction through the relevant nodes.
      
      Before a message got printed only for the last reduction it went
      through. So in case a node was reduced in-place several times
      in a row, only the last update was printed, or none at all if after
      being reduced in-place it got reduced by being replaced by another
      node: only the non-in-place replacement was showed. 
      
      Now each time an in-place reduction is applied to a node, a message
      gets printed.
      
      Bug: 
      Change-Id: Id0f816fecd44c01d0253966c6decc4861be0c2fa
      Reviewed-on: https://chromium-review.googlesource.com/563365Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Alexandre Talon <alexandret@google.com>
      Cr-Commit-Position: refs/heads/master@{#46552}
      7a75da34
  11. 08 Feb, 2017 1 commit
  12. 21 Apr, 2016 1 commit
  13. 11 Apr, 2016 1 commit
    • bmeurer's avatar
      [turbofan] Remove support for --turbo-types. · 086bc498
      bmeurer authored
      We had exactly one test case for --noturbo-types, so it's likely that
      the generic pipeline (without types) was already broken for quite some
      time, plus no one expressed interest in maintaining it, plus it
      complicates the JSGenericLowering integration. So decision is to kill
      it.
      
      R=jarin@chromium.org
      
      Review URL: https://codereview.chromium.org/1872333002
      
      Cr-Commit-Position: refs/heads/master@{#35387}
      086bc498
  14. 26 Feb, 2016 1 commit
    • bmeurer's avatar
      [turbofan] Don't use the CompareIC in JSGenericLowering. · d00da47b
      bmeurer authored
      The CompareICStub produces an untagged raw word value, which has to be
      translated to true or false manually in the TurboFan code. But for lazy
      bailout after the CompareIC, we immediately go back to fullcodegen or
      Ignition with the raw value, to a location where both fullcodegen and
      Ignition expect a boolean value, which might crash or in the worst case
      (depending on the exact computation inside the CompareIC) could lead to
      arbitrary memory access.
      
      Short-term fix is to use the proper runtime functions (unified with the
      interpreter now) for comparisons. Next task is to provide optimized
      versions of these based on the CodeStubAssembler, which can then be used
      via code stubs in TurboFan or directly in handlers in the interpreter.
      
      R=mstarzinger@chromium.org
      BUG=v8:4788
      LOG=n
      
      Review URL: https://codereview.chromium.org/1738153002
      
      Cr-Commit-Position: refs/heads/master@{#34335}
      d00da47b
  15. 16 Feb, 2016 1 commit
  16. 04 Sep, 2015 1 commit
  17. 01 Sep, 2015 1 commit
  18. 27 Aug, 2015 1 commit
  19. 15 Jun, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Remove the TryLowerDirectJSCall hack from generic lowering. · 6e5b9ffe
      bmeurer authored
      The TryLowerDirectJSCall method tried to lower to a direct JavaScript
      function call depending on the type of the receiver, but only if the
      target is a cosntant JSFunction. Since this depends on types and is not
      required for correctness, it shouldn't be part of generic lowering
      anyway. So this functionality was moved to typed lowering instead, and
      we use proper types for the target instead.
      
      R=mstarzinger@chromium.org
      
      Review URL: https://codereview.chromium.org/1182193005
      
      Cr-Commit-Position: refs/heads/master@{#29028}
      6e5b9ffe
  20. 20 Apr, 2015 1 commit
  21. 09 Mar, 2015 1 commit
  22. 17 Feb, 2015 1 commit
  23. 11 Feb, 2015 1 commit
    • svenpanne's avatar
      Removed most of the bogus CompilationInfo constructor calls. · d1b5aa07
      svenpanne authored
      A CompilationInfo constructed from just an Isolate* and a Zone* is in
      weird an inconsistent state (calling e.g. flags() on it will crash),
      so we need to avoid them. This CL removes almost all of them, the
      remaining 2 call sites in (for testing only) will be handled in a
      separate CL. Things which have been changed:
      
        * Linkage is basically a decorator for CallDescriptor now.
      
        * ChangeLowering doesn't need Linkage at all.
      
        * JSGenericLowering doesn't need a full CompilationInfo*, just a
          single flag.
      
        * JSContextSpecializer doesn't need the full CompilationInfo, just a
          Context.
      
        * Removed unused CompilationInfo from SimplifiedLoweringTester.
      
      This nicely decouples things already a bit more, but there's still
      work to do...
      
      Review URL: https://codereview.chromium.org/899803003
      
      Cr-Commit-Position: refs/heads/master@{#26580}
      d1b5aa07
  24. 23 Jan, 2015 1 commit
    • danno's avatar
      Remove the dependency of Zone on Isolate · c7b09aac
      danno authored
      Along the way:
      - Thread isolate parameter explicitly through code that used to
        rely on getting it from the zone.
      - Canonicalize the parameter position of isolate and zone for
        affected code
      - Change Hydrogen New<> instruction templates to automatically
        pass isolate
      
      R=mstarzinger@chromium.org
      LOG=N
      
      Review URL: https://codereview.chromium.org/868883002
      
      Cr-Commit-Position: refs/heads/master@{#26252}
      c7b09aac
  25. 22 Dec, 2014 1 commit
  26. 15 Dec, 2014 1 commit
  27. 10 Dec, 2014 1 commit
  28. 08 Dec, 2014 1 commit
  29. 27 Nov, 2014 2 commits
  30. 03 Nov, 2014 1 commit
  31. 31 Oct, 2014 2 commits
  32. 01 Oct, 2014 1 commit
  33. 30 Sep, 2014 1 commit
  34. 12 Sep, 2014 1 commit
  35. 11 Sep, 2014 1 commit
  36. 10 Sep, 2014 1 commit
  37. 29 Aug, 2014 1 commit