1. 29 Jul, 2021 1 commit
  2. 27 Jul, 2021 1 commit
  3. 26 Jul, 2021 1 commit
  4. 23 Jul, 2021 1 commit
  5. 22 Jul, 2021 1 commit
  6. 16 Jul, 2021 1 commit
  7. 12 Jul, 2021 1 commit
  8. 01 Jul, 2021 1 commit
    • Jakob Kummerow's avatar
      [bigint] Fix Karatsuba intermediate result length · a4b573e5
      Jakob Kummerow authored
      When adding up the results of the recursive steps, the Karatsuba
      algorithm can temporarily have intermediate results that are one
      bit bigger than the final result. This patch makes sure we handle
      that case correctly.
      Since that extra bit would always get subtracted again, the old
      code would not have caused incorrect results or memory corruption,
      but it did run into DCHECK-failures, and potentially could have
      caused segfaults.
      
      Bug: v8:11515, chromium:1223724
      Change-Id: I3592835d01cc36def8f0a9bae625e9249864ef78
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2988758Reviewed-by: 's avatarThibaud Michaud <thibaudm@chromium.org>
      Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#75509}
      a4b573e5
  9. 17 Jun, 2021 1 commit
  10. 15 Jun, 2021 1 commit
  11. 01 Jun, 2021 1 commit
  12. 31 May, 2021 1 commit
  13. 18 May, 2021 3 commits
  14. 06 May, 2021 1 commit
  15. 23 Apr, 2021 1 commit
  16. 08 Apr, 2021 2 commits
  17. 19 Mar, 2021 1 commit
  18. 15 Mar, 2021 1 commit
  19. 18 Feb, 2021 1 commit
  20. 11 Feb, 2021 1 commit
  21. 10 Feb, 2021 1 commit
    • Daniel Clark's avatar
      Fix top-level await crash from synthetic module being evaluated twice · f033e2a1
      Daniel Clark authored
      With top-level await, when Evaluate is performed on an already-evaluated
      synthetic module, Module::InnerEvaluate returns undefined.  This breaks
      top-level await's assumption that the returned value is always a
      promise.
      
      In order to make SyntheticModule's behavior consistent with
      SourceTextModule, the top_level_capability field is moved up to Module
      and SyntheticModule::Evaluate places the promise returned from the
      host's evaluation steps in that field.  Now SourceTextModule and
      SyntheticModule can share the same code to handle the case where the
      module is either kErrored or kEvaluated, so the code for this
      is moved up to Module.
      
      Thus, SyntheticModule is now guaranteed to return the
      promise from the evaluation steps even on subsequent Evaluate() calls.
      
      Unfortunately Node hasn't yet updated their EvaluationStepsCallback
      to return a Promise, so we can't yet assume that the returned value
      is a Promise without breaking Node.  So, this change also adds a clause
      to check for this condition and create a new resolved Promise if one
      was not provided by the callback steps.  This could eventually be
      removed once Node's callback steps are updated for top-level await.
      
      Change-Id: I2d6ae918abfeba9e3a757838502d4df92946edaa
      Bug: v8:11398
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2673794Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Commit-Queue: Dan Clark <daniec@microsoft.com>
      Cr-Commit-Position: refs/heads/master@{#72629}
      f033e2a1
  22. 04 Feb, 2021 1 commit
  23. 03 Feb, 2021 1 commit
  24. 26 Jan, 2021 3 commits
  25. 21 Jan, 2021 1 commit
  26. 24 Nov, 2020 1 commit
  27. 19 Nov, 2020 1 commit
  28. 12 Nov, 2020 2 commits
  29. 03 Nov, 2020 1 commit
  30. 29 Oct, 2020 1 commit
  31. 26 Oct, 2020 1 commit
  32. 24 Oct, 2020 1 commit
    • Camillo Bruni's avatar
      Reland "[runtime] Use Isolate::ThrowAt with MessageLocation" · 447915ef
      Camillo Bruni authored
      This is a reland of eb6b4ce1
      
      Skip test that serializes Error which references a Script. All errors
      created by ThrowAt store the current Script under the
      error_script_symbol.
      
      Original change's description:
      > [runtime] Use Isolate::ThrowAt with MessageLocation
      >
      > Fix various missing source positions when reporting parse and compile
      > errors. Namely this fixes missing source positions when having invalid
      > module imports.
      >
      > - Use Isolate::ThrowAt with valid MessageLocation objects
      > - Change public Isolate::Throw to no longer accept MessageLocation to
      >   avoid misues
      > - Introduce private Isolate::ThrowInternal that accepts MessageLocation
      >
      > Bug: v8:6513
      > Change-Id: I3ee633c9fff8c9d361bddb37f56e28a50c280ec1
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2467839
      > Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      > Reviewed-by: Marja Hölttä <marja@chromium.org>
      > Reviewed-by: Igor Sheludko <ishell@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#70623}
      
      Bug: v8:6513
      Change-Id: Icba74f74178e28fbda0fd0c237eeb7bacbc33570
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2487123Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Commit-Queue: Camillo Bruni <cbruni@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#70741}
      447915ef
  33. 28 Sep, 2020 1 commit
  34. 25 Sep, 2020 1 commit