1. 12 Nov, 2018 1 commit
  2. 12 Jun, 2018 1 commit
  3. 15 Mar, 2018 1 commit
  4. 13 Oct, 2017 1 commit
  5. 25 Sep, 2017 1 commit
  6. 23 Feb, 2017 1 commit
  7. 17 Oct, 2016 1 commit
  8. 20 Sep, 2016 1 commit
  9. 01 Apr, 2016 1 commit
  10. 09 Dec, 2015 1 commit
  11. 07 Dec, 2015 1 commit
  12. 30 Oct, 2015 1 commit
    • mstarzinger's avatar
      Move compiler cctests into v8::internal::compiler namespace. · 16f13300
      mstarzinger authored
      This moves all cctest files for the compiler to live in the same
      namespace as the components they are testing. Hence we can avoid the
      forbidden using directives pulling in entire namespaces.
      
      From the Google C++ style guide: "You may not use a using-directive to
      make all names from a namespace available". This would be covered by
      presubmit linter checks if build/namespaces were not blacklisted.
      
      R=bmeurer@chromium.org
      
      Review URL: https://codereview.chromium.org/1424943004
      
      Cr-Commit-Position: refs/heads/master@{#31671}
      16f13300
  13. 28 Oct, 2015 2 commits
  14. 20 Oct, 2015 1 commit
  15. 29 Apr, 2015 3 commits
  16. 15 Apr, 2015 1 commit
    • dcarney's avatar
      [turbofan] cleanup ParallelMove · 00aec790
      dcarney authored
      - make ParallelMove into a ZoneVector, removing an annoying level of indirection
      - make MoveOperands hold InstructionOperands instead of pointers, so there's no more operand aliasing for moves
      - opens up possibility of storing MachineType in allocated operands
      
      R=bmeurer@chromium.org
      BUG=
      
      Review URL: https://codereview.chromium.org/1081373002
      
      Cr-Commit-Position: refs/heads/master@{#27842}
      00aec790
  17. 31 Mar, 2015 1 commit
  18. 24 Mar, 2015 1 commit
  19. 23 Mar, 2015 1 commit
  20. 25 Feb, 2015 1 commit
  21. 12 Feb, 2015 1 commit
  22. 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
  23. 09 Feb, 2015 1 commit
  24. 04 Feb, 2015 1 commit
  25. 02 Feb, 2015 1 commit
  26. 30 Jan, 2015 3 commits
  27. 29 Jan, 2015 1 commit
  28. 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
  29. 22 Jan, 2015 1 commit
  30. 15 Jan, 2015 1 commit
  31. 18 Dec, 2014 2 commits
  32. 17 Dec, 2014 2 commits
  33. 14 Nov, 2014 1 commit