1. 26 Nov, 2012 1 commit
  2. 15 Nov, 2012 2 commits
  3. 24 Sep, 2012 1 commit
  4. 08 Aug, 2012 2 commits
  5. 11 Jul, 2012 1 commit
  6. 05 Jul, 2012 1 commit
  7. 05 Jun, 2012 1 commit
  8. 01 Jun, 2012 1 commit
    • rossberg@chromium.org's avatar
      Implement correct checking for inherited readonliness on assignment. · e4c472a7
      rossberg@chromium.org authored
      Removes 6 out of 8 of our remaining unintentional failures on test262.
      
      Also fixes treatment of inherited setters added after the fact.
      
      Specifically:
      
      - In the runtime, when looking for setter callbacks in the prototype chain,
        also look for read-only properties. If one is found, reject (exception in
        strict mode). If a proxy is found, invoke proper trap.
        Note: this folds in the CanPut function from the spec and avoids an extra
        lookup over the prototype chain.
      
      - In generated code for stores, insert a test for the maps from the prototype
        chain, but only up to the object where the property already exists (which
        may be the object itself).
        In Hydrogen, if the found property is read-only or not cacheable (e.g. a
        proxy), bail out; in a stub, generate an unconditional miss (to get an
        exception in strict mode).
      
      - Add test cases and adapt existing test expectations.
      
      R=mstarzinger@chromium.org
      BUG=
      TEST=
      
      Review URL: https://chromiumcodereview.appspot.com/10388047
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11694 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      e4c472a7
  9. 11 May, 2012 1 commit
  10. 23 Apr, 2012 1 commit
  11. 16 Apr, 2012 5 commits
  12. 13 Apr, 2012 1 commit
  13. 05 Apr, 2012 1 commit
  14. 28 Mar, 2012 1 commit
  15. 19 Mar, 2012 2 commits
  16. 15 Mar, 2012 1 commit
  17. 07 Mar, 2012 1 commit
  18. 01 Mar, 2012 1 commit
  19. 29 Feb, 2012 1 commit
  20. 24 Feb, 2012 2 commits
  21. 23 Feb, 2012 1 commit
    • mstarzinger@chromium.org's avatar
      Fix redefinition of aliased elements in arguments. · 1a356cff
      mstarzinger@chromium.org authored
      This refactors the way we (re)define elements to perform normalization
      and attribute updating at a much deeper level, thereby removing some
      bogus special cases in upper runtime layers.
      
      Most element setters take an indicator flag that distinguishes between
      setting and defining. Setting of an element causes attributes to remain
      unchanged, writability to be checked and callbacks to be called.
      Defining of an element causes attributes to be updated and callbacks to
      be overridden. The same approach could be taken for properties.
      
      R=svenpanne@chromium.org
      BUG=v8:1772
      TEST=test262,test262/15.2.3.6-4-333-11
      
      Review URL: https://chromiumcodereview.appspot.com/9443014
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10808 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      1a356cff
  22. 20 Feb, 2012 2 commits
  23. 17 Feb, 2012 2 commits
  24. 20 Dec, 2011 1 commit
  25. 16 Dec, 2011 2 commits
  26. 14 Dec, 2011 2 commits
  27. 12 Dec, 2011 1 commit
  28. 05 Dec, 2011 1 commit