1. 03 Jul, 2020 1 commit
  2. 09 Jun, 2020 1 commit
  3. 20 May, 2020 1 commit
    • Marja Hölttä's avatar
      [Promise.all] Use FixedArray for "values" · 7a85e029
      Marja Hölttä authored
      There's no need for it to be a JSArray. In the spec it's a List
      which roughly corresponds to FixedArray (but not JSArray).
      
      Gotchas:
      - There's no good point in time where we know the array length, since
      resolving might be interleaved with iteration.
      - Using ExtractFixedArray in places where we don't need to extract,
      since it takes care of things like allocating the resulting array
      in the right space etc.
      
      Drive-by fix: Previously we pre-allocated an array 1 elements too big,
      but never noticed it since the last element was the hole.
      
      Bug: v8:10506
      Change-Id: I6a72fbf1fc0cc031f2c8bad9314c4ed21d544a0f
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2202905Reviewed-by: 's avatarShu-yu Guo <syg@chromium.org>
      Commit-Queue: Marja Hölttä <marja@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#67919}
      7a85e029
  4. 12 May, 2020 2 commits
  5. 07 May, 2020 1 commit
  6. 06 May, 2020 1 commit
  7. 01 May, 2020 1 commit
    • Tobias Tebbi's avatar
      [torque] avoid ambiguity if a catch catches from other handlers · 7e7b24eb
      Tobias Tebbi authored
      Torque desugars try-catch/label constructs with several handlers
      into nested try structures, with the first handler ending-up
      innermost. So currently, if you write
      
      try {
      ...
      } label Foo {
        Throw(...);
      } catch (e) {
      
      }
      
      The catch will catch the preceding Throw in another handler.
      This is different from how multiple try-catch handlers are done in
      languages like Java, where throwing from a preceding catch handler
      is not caught by a later one. To avoid this possible ambiguity, this
      CL prohibits this pattern, enforcing that a catch handler comes first,
      before any other label-handler attached to the same try.
      This way, a catch handler never catches from any other handler on the
      same try, since they have to come later.
      
      Bug: v8:7793
      Change-Id: I943f14b2393d307c4254a3fc3a78f236dbcf86df
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2169098
      Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarNico Hartmann <nicohartmann@chromium.org>
      Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#67516}
      7e7b24eb
  8. 30 Apr, 2020 1 commit
  9. 28 Apr, 2020 1 commit
  10. 23 Apr, 2020 1 commit
  11. 21 Jan, 2020 1 commit