Skip to content

V
V8
Switch branch/tag
  1. 26 Jun, 2019 1 commit
  3. 23 May, 2019 2 commits
  5. 21 May, 2019 2 commits
  7. 21 Feb, 2019 1 commit
  9. 15 Feb, 2019 1 commit
  11. 14 Feb, 2019 1 commit
  13. 13 Feb, 2019 1 commit
  15. 28 Jan, 2019 1 commit
  17. 09 Jan, 2019 1 commit
  19. 08 Jan, 2019 1 commit
  21. 26 Dec, 2018 1 commit
  23. 20 Dec, 2018 1 commit
  25. 04 Dec, 2018 1 commit
  27. 26 Nov, 2018 1 commit
  29. 25 Nov, 2018 1 commit
  31. 24 Nov, 2018 1 commit
  33. 23 Nov, 2018 2 commits
  35. 22 Nov, 2018 1 commit
  37. 13 Nov, 2018 1 commit
  39. 05 Nov, 2018 1 commit
  41. 29 Oct, 2018 1 commit
  43. 24 Oct, 2018 1 commit
  45. 18 Oct, 2018 1 commit
  47. 10 Oct, 2018 1 commit
    • Marja Hölttä's avatar
      [js weak refs] Several fixes · ddbb12fa
      Marja Hölttä authored 
      1) As found by the GC fuzzer: missing HandleScopes.

2) The RecordSlot barrier was missing for NativeContext::AddDirtyJSWeakFactory.

3) Need Context::Scope to surround the cleanup function (if it results in an
error, we try to get native_context() from Isolate).

BUG=v8:8179,v8:8286

Change-Id: I2d995a76770658848e3c9629333bedbc2ef43b82
Reviewed-on: https://chromium-review.googlesource.com/c/1273051Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
Commit-Queue: Marja Hölttä <marja@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56529}
      ddbb12fa
  49. 09 Oct, 2018 1 commit
  51. 29 Sep, 2018 1 commit
    • Benedikt Meurer's avatar
      [async-await] Unify handling of await closure contexts. · 9e99297e
      Benedikt Meurer authored 
      Change the way that the (internal) await closures store the link to the
generator object by introducing a dedicated AwaitContext, which stores
the generator object into the extension slot (instead of misusing a
regular FunctionContext here). Also unify the allocation+initialization
of these contexts in the await-related builtins (both for async functions
and generators).

The rationale behind this is that for (zero-cost) async stack traces, we
will need to dig into these contexts and we can do better checking with
a dedicated instance type there. As an additional benefit, we save one
word per await context, since we just use (the otherwise unused) extension
slot to remember the generator object. As yet another benefit we will
never accidentally use any of these contexts in the regular scope chain
lookups, meaning we can also catch bugs there. And last but not least
the objects printing machinery understands these contexts now and can
even print the generator object for AwaitContexts for short printing,
which is really valuable for debugging.

Tbr: ulan@chromium.org
Bug: v8:7253, v8:7522, v8:8015
Change-Id: I86955f5701e694e8a10b91ebe5f52705aa90968d
Reviewed-on: https://chromium-review.googlesource.com/1249491Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56301}
      9e99297e
  53. 24 Aug, 2018 1 commit
  55. 30 Jul, 2018 1 commit
  57. 17 Jul, 2018 1 commit
  59. 05 Jul, 2018 1 commit
  61. 19 Jun, 2018 1 commit
  63. 15 Jun, 2018 1 commit
  65. 12 Jun, 2018 1 commit
  67. 03 May, 2018 1 commit
  69. 23 Mar, 2018 3 commits