• 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
test262.status 4.22 KB