1. 24 Sep, 2015 2 commits
    • danno's avatar
      Revert of Remove register index/code indirection (patchset #17 id:320001 of... · 3ac27431
      danno authored
      Revert of Remove register index/code indirection (patchset #17 id:320001 of https://codereview.chromium.org/1287383003/ )
      
      Reason for revert:
      Failures on greedy RegAlloc, Fuzzer
      
      Original issue's description:
      > Remove register index/code indirection
      >
      > Previous to this patch, both the lithium and TurboFan register
      > allocators tracked allocated registers by "indices", rather than
      > the register codes used elsewhere in the runtime. This patch
      > ensures that codes are used everywhere, and in the process cleans
      > up a bunch of redundant code and adds more structure to how the
      > set of allocatable registers is defined.
      >
      > Some highlights of changes:
      >
      > * TurboFan's RegisterConfiguration class moved to V8's top level
      >   so that it can be shared with Crankshaft.
      > * Various "ToAllocationIndex" and related methods removed.
      > * Code that can be easily shared between Register classes on
      >   different platforms is now shared.
      > * The list of allocatable registers on each platform is declared
      >   as a list rather than implicitly via the register index <->
      >   code mapping.
      >
      > Committed: https://crrev.com/80bc6f6e11f79524e3f1ad05579583adfd5f18b2
      > Cr-Commit-Position: refs/heads/master@{#30913}
      
      TBR=akos.palfi@imgtec.com,bmeurer@chromium.org,jarin@chromium.org,paul.lind@imgtec.com,titzer@chromium.org
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1365073002
      
      Cr-Commit-Position: refs/heads/master@{#30914}
      3ac27431
    • danno's avatar
      Remove register index/code indirection · 80bc6f6e
      danno authored
      Previous to this patch, both the lithium and TurboFan register
      allocators tracked allocated registers by "indices", rather than
      the register codes used elsewhere in the runtime. This patch
      ensures that codes are used everywhere, and in the process cleans
      up a bunch of redundant code and adds more structure to how the
      set of allocatable registers is defined.
      
      Some highlights of changes:
      
      * TurboFan's RegisterConfiguration class moved to V8's top level
        so that it can be shared with Crankshaft.
      * Various "ToAllocationIndex" and related methods removed.
      * Code that can be easily shared between Register classes on
        different platforms is now shared.
      * The list of allocatable registers on each platform is declared
        as a list rather than implicitly via the register index <->
        code mapping.
      
      Review URL: https://codereview.chromium.org/1287383003
      
      Cr-Commit-Position: refs/heads/master@{#30913}
      80bc6f6e
  2. 11 Sep, 2015 1 commit
  3. 20 Apr, 2015 1 commit
  4. 12 Dec, 2014 1 commit
  5. 11 Sep, 2014 1 commit
  6. 10 Sep, 2014 1 commit
  7. 05 Sep, 2014 2 commits
  8. 04 Sep, 2014 1 commit
  9. 03 Sep, 2014 3 commits
  10. 02 Sep, 2014 1 commit
  11. 25 Aug, 2014 1 commit
  12. 22 Aug, 2014 1 commit
  13. 04 Aug, 2014 1 commit
  14. 03 Jul, 2014 1 commit
  15. 30 Jun, 2014 1 commit
  16. 20 Jun, 2014 1 commit
  17. 11 Jun, 2014 1 commit
  18. 03 Jun, 2014 1 commit
  19. 13 May, 2014 1 commit
  20. 09 May, 2014 1 commit
  21. 30 Apr, 2014 1 commit
  22. 29 Apr, 2014 1 commit
  23. 24 Apr, 2014 1 commit
    • svenpanne@chromium.org's avatar
      CodeStubs contain their corresponding Isolate* now. (part 1) · dd30db90
      svenpanne@chromium.org authored
      This is a purely mechanical change, adding an Isolate* to the CodeStub
      constructor and a corresponding field plus a getter. A few methods in
      CodeStub and its subclasses can be simplified now, but this is done in
      a separate CL.
      
      The underlying reason apart from simplicity is that deep down in the
      call chain we need to detect if the serializer is active or not. This
      information will be part of the Isolate, not a global variable with
      funky synchronization primitives around it (which is fundamentally
      wrong and the underlying cause for race conditions and a catch-22
      during initialization).
      
      BUG=359977
      LOG=y
      R=mstarzinger@chromium.org
      
      Review URL: https://codereview.chromium.org/246643014
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20919 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      dd30db90
  24. 19 Mar, 2014 1 commit
  25. 03 Mar, 2014 1 commit
  26. 22 Jan, 2014 1 commit
  27. 18 Dec, 2013 1 commit
  28. 29 Nov, 2013 1 commit
  29. 18 Oct, 2013 1 commit
  30. 24 Sep, 2013 1 commit
  31. 23 Sep, 2013 2 commits
  32. 19 Sep, 2013 1 commit
  33. 11 Sep, 2013 1 commit
  34. 19 Jul, 2013 2 commits