1. 20 Feb, 2017 1 commit
  2. 13 Jan, 2017 3 commits
  3. 30 Nov, 2016 1 commit
    • caitp's avatar
      [accessors] handle `writable` changing during ArrayLengthSetter · d4918463
      caitp authored
      The "writable" property descriptor may legally change during the call to
      AnythingToArrayLength(). This change needs to be honoured before calling
      JSArray::SetLength(). The change is only honoured when the "length"
      property was previously writable, so that changes during a call to
      DefineOwnPropertyIgnoreAttributes() is ignored.
      
      BUG=v8:5688
      R=cbruni@chromium.org, verwaest@chromium.org, jkummerow@chromium.org
      
      Review-Url: https://codereview.chromium.org/2543553002
      Cr-Commit-Position: refs/heads/master@{#41396}
      d4918463
  4. 29 Nov, 2016 1 commit
    • mstarzinger's avatar
      [deoptimizer] Fix deoptimization in {TranslatedState}. · 204babf5
      mstarzinger authored
      This ensures the deoptimization triggered due to materialization of
      objects by the {TranslatedState} works in conjunction with OSR. The
      optimized code used for OSR is not installed on the function, hence
      needs to be specified explicitly when requesting deoptimization for
      specific stack frames.
      
      R=jarin@chromium.org
      TEST=mjsunit/regress/regress-crbug-668795
      BUG=chromium:668795
      
      Review-Url: https://codereview.chromium.org/2534143002
      Cr-Commit-Position: refs/heads/master@{#41348}
      204babf5
  5. 17 Nov, 2016 3 commits
  6. 16 Nov, 2016 2 commits
  7. 10 Nov, 2016 1 commit
  8. 28 Oct, 2016 1 commit
  9. 26 Oct, 2016 1 commit
    • neis's avatar
      [runtime] Let native setters have a return value. · f33a4078
      neis authored
      Native setters (see AccessorInfo in accessors.h) didn't have the ability
      to return a result value. As a consequence of this, for instance, Reflect.set
      on the length property of arrays had the wrong behavior:
      
      var y = [];
      Object.defineProperty(y, 0, {value: 42, configurable: false})
      Reflect.set(y, 'length', 0)
      
      The Reflect.set call used to return true. Now it returns false as
      required by the spec.
      
      BUG=v8:5401
      
      Review-Url: https://codereview.chromium.org/2397603003
      Cr-Commit-Position: refs/heads/master@{#40579}
      f33a4078
  10. 25 Oct, 2016 1 commit
  11. 11 Oct, 2016 1 commit
  12. 07 Oct, 2016 4 commits
  13. 03 Aug, 2016 1 commit
  14. 22 Jul, 2016 1 commit
  15. 20 Jul, 2016 2 commits
  16. 19 Jul, 2016 1 commit
  17. 07 Jul, 2016 1 commit
  18. 06 Jul, 2016 1 commit
    • neis's avatar
      [debugger] Don't leak holes from generator arguments. · 45a81674
      neis authored
      This is a quick fix for the hole leaking from generators via the debugger's frame
      inspection feature: when collecting the arguments, convert each hole to undefined.
      In the long term, we probably want to remember and restore the actual arguments
      rather than pushing these dummy arguments on each resume.
      
      BUG=v8:5164
      
      Review-Url: https://codereview.chromium.org/2122923003
      Cr-Commit-Position: refs/heads/master@{#37544}
      45a81674
  19. 28 Jun, 2016 1 commit
  20. 27 Jun, 2016 2 commits
  21. 06 Jun, 2016 1 commit
  22. 19 May, 2016 3 commits
  23. 13 May, 2016 2 commits
    • gsathya's avatar
      Revert "Fix TypedArray Property optimizations", add regression test and eliminate dead code · d33aedb7
      gsathya authored
      This reverts commit 41d571df.
      
      Reason for revert: This patch breaks the correctness of the typedarray
      properties such as length, byteOffset, byteLength.
      
      The accessor check optimization code is dead code eliminated. A follow
      up patch will fix this optimization correctly.
      
      BUG=chromium:593634
      
      Review-Url: https://codereview.chromium.org/1977983002
      Cr-Commit-Position: refs/heads/master@{#36254}
      d33aedb7
    • verwaest's avatar
      [runtime] Make sure that LookupIterator::OWN always performs a HIDDEN lookup as well. · c9a83150
      verwaest authored
      Hidden prototypes are merely an implementation detail. Properties on an object + hidden prototype should look like properties on the object. Hence we should always perform a hidden prototype lookup. This CL removes the option to ignore hidden prototypes to avoid bugs that leak this implementation detail.
      
      Also, the only previously valid cases were either places were we knew we didn't have a hidden prototype; or because we knew we (in the optimizing compiler) would only handle properties from the non-hidden object.The first case is already handled by directly tagging whether a receiver has a hidden prototype. In the second case we can just filter out properties from hidden prototypes.
      
      Review-Url: https://codereview.chromium.org/1975763002
      Cr-Commit-Position: refs/heads/master@{#36235}
      c9a83150
  24. 09 May, 2016 3 commits
  25. 06 May, 2016 1 commit