1. 18 Mar, 2020 1 commit
  2. 29 Jan, 2020 1 commit
  3. 23 Jan, 2020 1 commit
  4. 21 Jan, 2020 1 commit
  5. 16 Jan, 2020 1 commit
  6. 13 Jan, 2020 1 commit
  7. 07 Jan, 2020 1 commit
  8. 19 Dec, 2019 2 commits
  9. 16 Dec, 2019 1 commit
  10. 13 Dec, 2019 1 commit
  11. 06 Dec, 2019 1 commit
  12. 28 Nov, 2019 1 commit
  13. 26 Nov, 2019 1 commit
  14. 22 Nov, 2019 1 commit
  15. 08 Nov, 2019 1 commit
  16. 01 Nov, 2019 1 commit
  17. 30 Oct, 2019 1 commit
  18. 16 Oct, 2019 1 commit
  19. 19 Sep, 2019 1 commit
  20. 17 Sep, 2019 1 commit
  21. 26 Aug, 2019 1 commit
  22. 23 Aug, 2019 1 commit
  23. 27 May, 2019 2 commits
    • Tobias Tebbi's avatar
      [torque] no longer generate assemblers per namespace · 19d8bfa5
      Tobias Tebbi authored
      Instead of generating one CodeStubAssembler-like class per namespace,
      Torque-generated macros are now free-standing functions not included
      from CSA code, and explicitly exported macros become part of the new
      TorqueGeneratedExportedMacrosAssembler, which CodeStubAssembler
      inherits from, thus making them available to all CSA code.
      
      Structs are now defined in a new header csa-types-tq.h as free-standing
      types with the prefix "TorqueStruct".
      
      This is a preparation for generating per Torque-file instead of per
      namespace.
      
      Change-Id: I60fadc493a63f85d1d340768ec6f11ae47be0cb8
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1628787
      Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarSigurd Schneider <sigurds@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61865}
      19d8bfa5
    • Clemens Hammacher's avatar
      [cleanup] Replace simple typedefs by using · a335f2ae
      Clemens Hammacher authored
      This replaces all typedefs that define types and not functions by the
      equivalent "using" declaration.
      
      This was done mostly automatically using this command:
      ag -l '\btypedef\b' src test | xargs -L1 \
           perl -i -p0e 's/typedef ([^*;{}]+) (\w+);/using \2 = \1;/sg'
      
      Patchset 2 then adds some manual changes for typedefs for pointer types,
      where the regular expression did not match.
      
      R=mstarzinger@chromium.org
      TBR=yangguo@chromium.org, jarin@chromium.org
      
      Bug: v8:9183
      Change-Id: I6f6ee28d1793b7ac34a58f980b94babc21874b78
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1631409
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61849}
      a335f2ae
  24. 21 May, 2019 1 commit
  25. 14 May, 2019 1 commit
  26. 23 Apr, 2019 1 commit
  27. 12 Apr, 2019 1 commit
  28. 10 Apr, 2019 1 commit
    • Sathya Gunasekaran's avatar
      [promise] Refactor Promise.all · 5bcaca3a
      Sathya Gunasekaran authored
      The resolve/reject callbacks to PerformPromiseAll is refactored out so
      that we can just pass different closures for PerformPromiseAllSettled.
      
      Similarly, a closure to update the value is passed to
      Generate_PromiseAllResolveElementClosure so that we can create a
      diferrent value in case of Promise.allSettled.
      
      Bug: v8:9060
      Change-Id: I4e1bebe6da4ea0965a67cccc8365ed91cf4683c7
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1559216
      Auto-Submit: Sathya Gunasekaran <gsathya@chromium.org>
      Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#60732}
      5bcaca3a
  29. 04 Apr, 2019 1 commit
  30. 26 Feb, 2019 1 commit
  31. 18 Feb, 2019 1 commit
  32. 13 Dec, 2018 1 commit
  33. 12 Dec, 2018 2 commits
  34. 19 Nov, 2018 1 commit
  35. 05 Nov, 2018 1 commit
    • Tobias Tebbi's avatar
      [torque] qualified access to CSA assemblers · 23b48920
      Tobias Tebbi authored
      No longer use inheritance to associate Torque-generated assemblers
      with corresponding CSA subclasses. Instead, all references to CSA
      and CSA-derived assemblers are now explicitly qualified, by generating
      a short-lived assembler instance in-place. As a consequence, Torque
      files have to mention the assembler external macros live in.
      The CodeStubAssembler is the default for this and can be omitted.
      As a drive-by cleanup, also distinguish between names that are emitted
      in C++ and names that are intended to be read in error messages. This
      is relevant for generic instantiations, where the generated names are
      rather unreadably mangled.
      
      As a follow-up, it will be easy to allow for qualified access to
      different modules, thus implementing full namespace semantics for
      modules.
      
      Bug: v8:7793
      Change-Id: Ie6f1b6b549b510fb49be2442393d898d5f130950
      Reviewed-on: https://chromium-review.googlesource.com/c/1309636
      Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarDaniel Clifford <danno@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#57235}
      23b48920
  36. 31 Oct, 2018 1 commit
  37. 26 Oct, 2018 1 commit
    • Benedikt Meurer's avatar
      [async] Add Promise.all() support to --async-stack-traces. · 6f39ab89
      Benedikt Meurer authored
      This adds support for Promise.all() to --async-stack-traces (also at
      zero cost, since we can derive the relevant information from the resolve
      element closure and context). In case of `Promise.all(a)` the stack
      trace even tells you which element of `a` is responsible, for example
      
      ```js
      async function fine() {}
      async function thrower() { await fine(); throw new Error(); }
      async function test() { await Promise.all([fine(), thrower()]); }
      ```
      
      will generate the following stack trace
      
      ```
      Error
          at thrower (something.js:1:9)
          at async Promise.all (index 1)
          at async test (something.js:3:3)
      ```
      
      so it not only shows the async Promise.all() frames, but even tells the
      user exactly that the second element of `[fine(), thrower()]` is the
      relevant one.
      
      Bug: v8:7522
      Change-Id: I279a845888e06053cf0e3c9338ab71caabaabf45
      Reviewed-on: https://chromium-review.googlesource.com/c/1299248Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#57023}
      6f39ab89