1. 26 Nov, 2020 1 commit
  2. 06 Nov, 2020 1 commit
  3. 28 Nov, 2019 1 commit
  4. 24 May, 2019 1 commit
  5. 29 Mar, 2019 1 commit
  6. 17 Sep, 2018 1 commit
  7. 12 Jun, 2017 1 commit
  8. 10 May, 2017 1 commit
  9. 25 Feb, 2017 1 commit
  10. 26 Jan, 2017 1 commit
  11. 25 Oct, 2016 1 commit
  12. 17 Oct, 2016 1 commit
  13. 20 Sep, 2016 1 commit
  14. 25 May, 2016 1 commit
  15. 02 Feb, 2016 1 commit
    • danno's avatar
      [compiler] Extend the functionality of CodeStubAssembler · 1f28904b
      danno authored
      After this change, the functionality of the CodeStubAssembler should be
      sufficient to generate non-trivial stubs (e.g. the KeyedLoadIC) with control
      flow, variables and probing of internal meta data structures.
      
      Specifically this patch:
      
      * introduces a Label class, which allows stubs to construct graphs that don't
        have linear control graphs.
      * introduces a Variable class. Variables can be bound to Node* values at
        different points in a non-linear control flow graph. In conjunction with the
        Label machinery, the CodeStubAssembler ensures that Phi nodes are inserted at
        the "minimal" set of merge points.
      * adds Tail calling support to other Stubs and to any arbitrary code whose
        interface can be described by a CallInterfaceDescriptor.
      * provides new macros for accessing FixedArray elements that are optimized for
        use with Smi values.
      
      Review URL: https://codereview.chromium.org/1649723002
      
      Cr-Commit-Position: refs/heads/master@{#33664}
      1f28904b
  16. 14 Jan, 2016 1 commit
  17. 23 Sep, 2015 3 commits
  18. 19 Jun, 2015 1 commit
  19. 17 Jun, 2015 1 commit
  20. 12 Jun, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Use appropriate type for NodeId. · c487aba7
      bmeurer authored
      Up until now we used int32_t for NodeId, but that was not ideal because
      negative values are invalid for NodeId and we use it as an array index
      for example in the NodeMarker class, where C++ compilers on x64 have to
      generate code that does proper sign extension for the indices, which is
      completely unnecessary.
      
      R=svenpanne@chromium.org
      
      Review URL: https://codereview.chromium.org/1178403004
      
      Cr-Commit-Position: refs/heads/master@{#28997}
      c487aba7
  21. 01 Jun, 2015 1 commit
  22. 23 Apr, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Unify frame state inputs. · 4940c0bd
      bmeurer authored
      Now all nodes that care about deoptimization always take frame state
      inputs no matter whether deoptimization is enabled for a particular
      function. In case that deoptimization is off, the AstGraphBuilder just
      inserts the empty frame state. This greatly simplifies the logic in
      various places and makes testing easier as well, and is probably the
      first step towards enabling --turbo-deoptimization by default.
      
      There seems to be no noticable performance impact on asm.js programs.
      
      Also fix the graph replay in order to regenerate the scheduler unittests.
      
      Review URL: https://codereview.chromium.org/1106613003
      
      Cr-Commit-Position: refs/heads/master@{#28026}
      4940c0bd
  23. 05 Feb, 2015 1 commit
  24. 07 Jan, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Cleanup Graph and related classes. · e53845d4
      bmeurer authored
      - Move NodeMarker to its own file, and introduce a non
        templatized base class.
      - Cleanup the include hell.
      - Sanitize the Node construction methods now that we
        got rid of that GenericNode/GenericGraph stuff.
      - Protect against NodeId overflow in Graph.
      - Various minor cleanups.
      
      TEST=cctest,mjsunit,unittests
      
      Review URL: https://codereview.chromium.org/838783002
      
      Cr-Commit-Position: refs/heads/master@{#25977}
      e53845d4
  25. 12 Dec, 2014 1 commit
  26. 02 Dec, 2014 1 commit
  27. 28 Nov, 2014 3 commits
  28. 20 Oct, 2014 1 commit
  29. 15 Oct, 2014 1 commit
    • rossberg@chromium.org's avatar
      Better typing and type verification · 0e16150d
      rossberg@chromium.org authored
      - Extend verifier to check types of JS and Simplified nodes.
      - Untyped nodes now contain NULL as types, enforcing hard failure.
      - Typer immediately installs itself as a decorator; remove explicit decorator installation.
      - Decorator eagerly types all nodes that have typed inputs
        (subsumes typing of constant cache, removing its typing
        side-channel and various spurious dependencies on the typer).
      - Cut down typer interface to prevent inconsistently typed graphs.
      - Remove verification from start, since it caused too much trouble
        with semi-wellformed nodes.
      - Fix a couple of bugs on the way that got uncovered.
      
      To do: verifying machine operators. Also, various conditions in the
      verifier are currently commented out, because they don't yet hold.
      
      BUG=
      R=jarin@chromium.org,titzer@chromium.org
      
      Review URL: https://codereview.chromium.org/658543002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24626 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      0e16150d
  30. 04 Sep, 2014 1 commit
  31. 26 Aug, 2014 2 commits
  32. 04 Aug, 2014 1 commit
  33. 30 Jul, 2014 1 commit