1. 27 Apr, 2019 1 commit
  2. 18 Apr, 2019 1 commit
  3. 12 Apr, 2019 1 commit
  4. 11 Apr, 2019 1 commit
  5. 09 Apr, 2019 1 commit
  6. 04 Apr, 2019 1 commit
  7. 26 Feb, 2019 1 commit
  8. 26 Dec, 2018 1 commit
  9. 18 Dec, 2018 1 commit
  10. 17 Dec, 2018 1 commit
  11. 14 Dec, 2018 2 commits
  12. 08 Dec, 2018 1 commit
  13. 29 Nov, 2018 1 commit
  14. 25 Nov, 2018 1 commit
  15. 23 Nov, 2018 1 commit
  16. 19 Nov, 2018 1 commit
  17. 16 Nov, 2018 2 commits
  18. 14 Nov, 2018 1 commit
  19. 13 Nov, 2018 2 commits
  20. 06 Nov, 2018 1 commit
  21. 10 Oct, 2018 1 commit
    • Hai Dang's avatar
      Add iterator protectors for JSMapIterator/JSSet/JSSetIterator. · 60d3ce72
      Hai Dang authored
      The MapIterator protector protects the original iteration behaviors of
      Map.prototype.keys(), Map.prototype.values(), and Set.prototype.entries().
      It does not protect the original iteration behavior of
      Map.prototype[Symbol.iterator](). The protector is invalidated when:
      * The 'next' property is set on an object where the property holder is the
        %MapIteratorPrototype% (e.g. because the object is that very prototype).
      * The 'Symbol.iterator' property is set on an object where the property
        holder is the %IteratorPrototype%. Note that this also invalidates the
        SetIterator protector (see below).
      
      The SetIterator protector protects the original iteration behavior of
      Set.prototype.keys(), Set.prototype.values(), Set.prototype.entries(),
      and Set.prototype[Symbol.iterator](). The protector is invalidated when:
      * The 'next' property is set on an object where the property holder is the
        %SetIteratorPrototype% (e.g. because the object is that very prototype).
      * The 'Symbol.iterator' property is set on an object where the property
        holder is the %SetPrototype% OR %IteratorPrototype%. This means that
        setting Symbol.iterator on a MapIterator object can also invalidate the
        SetIterator protector, and vice versa, setting Symbol.iterator on a
        SetIterator object can also invalidate the MapIterator. This is an over-
        approximation for the sake of simplicity.
      
      Bug: v8:7980
      Change-Id: I54ad6e4c7f19ccc27d7001f6c4b6c8d6ea4ee871
      Reviewed-on: https://chromium-review.googlesource.com/c/1273102Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Commit-Queue: Hai Dang <dhai@google.com>
      Cr-Commit-Position: refs/heads/master@{#56530}
      60d3ce72
  22. 01 Oct, 2018 1 commit
  23. 11 Sep, 2018 1 commit
  24. 13 Aug, 2018 1 commit
  25. 31 Jul, 2018 1 commit
  26. 17 Jul, 2018 1 commit
  27. 13 Jul, 2018 1 commit
  28. 10 Jul, 2018 1 commit
    • Benedikt Meurer's avatar
      [async-generators] Add fast-path to skip "then" lookup in AsyncGeneratorResolve. · cf080aeb
      Benedikt Meurer authored
      This extends the Promise#then protector to also guard the intrinsic
      %ObjectPrototype%, making it usable for fast-path logic in the
      AsyncGeneratorResolve operation, where we can skip the "then" lookup
      on the iteratorResult in that case. We also add a corresponding fast-
      path to the ResolvePromise builtin itself, which avoids the second
      "then" lookup on the async iterator side.
      
      This reduces execution time of the fibonacci-async-es2017-native test
      from 298.16ms to 280.55ms, which corresponds to an improvement of ~6%
      in this case.
      
      This is a rebased reland of
      
        https://chromium-review.googlesource.com/967203
      
      which landed earlier, but had to be reverted as part of the mega-revert
      that was necessary to fix the async_hooks breakage in Node 10.
      
      Bug: v8:7253
      Change-Id: Id9dd1ddc4a8285d64e92cd2030f3168a12e4b509
      Reviewed-on: https://chromium-review.googlesource.com/1130523
      Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarMaya Lekova <mslekova@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54352}
      cf080aeb
  29. 04 Jul, 2018 1 commit
  30. 26 Jun, 2018 1 commit
    • Georg Neis's avatar
      Reland "Reland "Introduce MutableHeapNumber class."" · f1c79e02
      Georg Neis authored
      This is a reland of f0bcbc90.
      A few casts were still wrong.
      
      Original change's description:
      > Reland "Introduce MutableHeapNumber class."
      >
      > This is a reland of 40ac6b18, which
      > was incorrect due to a bad merge.
      >
      > Original change's description:
      > > Introduce MutableHeapNumber class.
      > >
      > > V8 knows heap numbers and mutable heap numbers. They have
      > > difference instance types, but in C++ code we've used the
      > > same class for both (HeapNumber). Confusingly, however,
      > > IsHeapNumber would return false for mutable heap numbers,
      > > while HeapNumber::cast would succeed.
      > >
      > > This CL adds a separate class MutableHeapNumber and
      > > eliminates the confusing behavior.
      > >
      [...]
      > TBR=bmeurer@chromium.org
      > TBR=ulan@chromium.org
      >
      > Change-Id: I3af1014c949821dfac0754a3e48c65ce1bad1ad1
      > Reviewed-on: https://chromium-review.googlesource.com/1114539
      > Reviewed-by: Georg Neis <neis@chromium.org>
      > Commit-Queue: Georg Neis <neis@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#54022}
      
      Change-Id: I19a33da4b6abcd445b528a84d4f56ba1964d337b
      Reviewed-on: https://chromium-review.googlesource.com/1114100
      Commit-Queue: Georg Neis <neis@chromium.org>
      Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54027}
      f1c79e02
  31. 25 Jun, 2018 1 commit
  32. 23 Jun, 2018 2 commits
  33. 21 Jun, 2018 1 commit
  34. 19 Jun, 2018 1 commit
  35. 11 Jun, 2018 1 commit
  36. 04 Jun, 2018 1 commit