1. 30 Sep, 2014 1 commit
  2. 15 Sep, 2014 1 commit
  3. 08 Sep, 2014 3 commits
  4. 05 Sep, 2014 1 commit
  5. 04 Sep, 2014 1 commit
  6. 01 Sep, 2014 1 commit
  7. 25 Aug, 2014 1 commit
  8. 22 Aug, 2014 1 commit
  9. 11 Aug, 2014 3 commits
  10. 06 Aug, 2014 1 commit
  11. 04 Aug, 2014 1 commit
  12. 30 Jul, 2014 2 commits
  13. 22 Jul, 2014 1 commit
  14. 21 Jul, 2014 1 commit
  15. 17 Jul, 2014 2 commits
  16. 07 Jul, 2014 1 commit
  17. 03 Jul, 2014 1 commit
  18. 01 Jul, 2014 1 commit
  19. 30 Jun, 2014 3 commits
  20. 25 Jun, 2014 1 commit
    • mvstanton@chromium.org's avatar
      The IC exposes a register definition. · addd35df
      mvstanton@chromium.org authored
      Centralize a register definition in an IC that provides:
      1) symbolic names for the register (like, edx == receiver)
      2) defines ordering when passed on the stack
      
      Code that implements or uses the IC should use this definition instead of "knowing" what the registers are. Or at least have the definition to validate it's assumptions.
      
      As a side effect of avoiding runtime static initializers (enforced by tools/check-static-initializers.sh, neat), I gave ownership of the registers array to CodeStubInterfaceDescriptor. This prompted a cleanup of that struct.
      
      R=jkummerow@chromium.org
      
      Review URL: https://codereview.chromium.org/352583002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22011 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      addd35df
  21. 10 Jun, 2014 2 commits
  22. 06 Jun, 2014 1 commit
  23. 03 Jun, 2014 1 commit
  24. 27 May, 2014 1 commit
  25. 26 May, 2014 2 commits
  26. 09 May, 2014 1 commit
  27. 29 Apr, 2014 1 commit
  28. 25 Apr, 2014 2 commits
  29. 24 Apr, 2014 1 commit