1. 14 Jul, 2022 1 commit
  2. 13 Jul, 2022 2 commits
  3. 12 Jul, 2022 1 commit
  4. 11 Jul, 2022 1 commit
  5. 09 Jul, 2022 1 commit
    • Leszek Swirski's avatar
      Revert "Reland "[flags] Enable freezing of flags"" · 666d559e
      Leszek Swirski authored
      This reverts commit d34170f2.
      
      Reason for revert: "The (hopefully) last issue in chromium is fixed"
        Narrator: It wasn't -- https://ci.chromium.org/ui/p/chromium/builders/try/cast_shell_linux/1260757/overview
      
      Original change's description:
      > Reland "[flags] Enable freezing of flags"
      >
      > This is a reland of commit 1ed7d0b8.
      > The (hopefully) last issue in chromium is fixed in https://crrev.com/c/3745533.
      >
      > Original change's description:
      > > [flags] Enable freezing of flags
      > >
      > > This enables the --freeze-flags-after-init flag globally. Note that
      > > tests, fuzzers, Node and other still explicitly disable the flag. The
      > > chrome renderer process and default d8 execution will have it enabled
      > > though.
      > >
      > > R=cbruni@chromium.org
      > >
      > > Bug: v8:12887
      > > Change-Id: I9a15ef64227e5e6e04779d8d671a2c50d99c9097
      > > Cq-Include-Trybots: luci.v8.try:v8_linux_blink_rel
      > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3695264
      > > Reviewed-by: Camillo Bruni <cbruni@chromium.org>
      > > Commit-Queue: Clemens Backes <clemensb@chromium.org>
      > > Cr-Commit-Position: refs/heads/main@{#81214}
      >
      > Bug: v8:12887
      > Change-Id: I6445c04abc55242d6e2f204d45ec9ce22c6ece34
      > Cq-Include-Trybots: luci.v8.try:v8_linux_blink_rel
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3707284
      > Reviewed-by: Camillo Bruni <cbruni@chromium.org>
      > Commit-Queue: Clemens Backes <clemensb@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#81603}
      
      No-try: true
      Bug: v8:12887
      Change-Id: I73e0a52974a2730386e805b7de98de8d87e2d208
      Cq-Include-Trybots: luci.v8.try:v8_linux_blink_rel
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3749584
      Auto-Submit: Leszek Swirski <leszeks@chromium.org>
      Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Commit-Queue: Leszek Swirski <leszeks@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#81621}
      666d559e
  6. 08 Jul, 2022 2 commits
  7. 07 Jul, 2022 1 commit
  8. 05 Jul, 2022 1 commit
  9. 04 Jul, 2022 1 commit
  10. 30 Jun, 2022 1 commit
  11. 29 Jun, 2022 1 commit
  12. 28 Jun, 2022 1 commit
  13. 27 Jun, 2022 1 commit
  14. 22 Jun, 2022 2 commits
  15. 21 Jun, 2022 1 commit
  16. 17 Jun, 2022 3 commits
  17. 15 Jun, 2022 1 commit
  18. 14 Jun, 2022 2 commits
  19. 13 Jun, 2022 2 commits
    • Clemens Backes's avatar
      [wasm] Add flag to limit module size · dc748570
      Clemens Backes authored
      Add a new --wasm-max-module-size flag to replace the unused and more
      specific --experimental-wasm-allow-huge-modules flag.
      The new flag can be used in fuzzers to reduce the maximum allowed module
      size, avoiding OOM on some systems (like 32-bit ASan builds).
      
      R=ahaas@chromium.org
      
      Bug: chromium:1334577
      Change-Id: I2830d407c5b01be21a47b21392c1210061c40b20
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3695267Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#81102}
      dc748570
    • Simon Zünd's avatar
      [debug] Allow live-editing of top-most frame · 79db56f1
      Simon Zünd authored
      This CL extends the live edit mechanism to allow editing the function
      that is currently on top of the stack, as long as that call frame is
      the only activation of that  function.
      
      The CL changes how we look for functions on the current JS stack:
      Instead of starting at thread_local_top we start at the frame we
      are currently paused in. This is possible since there can not be any
      JavaScript frames above the current "break frame", only C++ frames
      which are not relevant for live edit.
      
      If the edited script modifes the top-most function, the inspector
      will trigger a restart of that call frame. That is why we check
      if we can actually restart the function and only allow the live
      edit to go through if that is the case.
      
      Note that this CL also adds a kill switch in the form of a runtime
      flag for this feature, in case we need to pull the plug and disable
      this feature again via back-merge.
      
      R=jarin@chromium.org
      
      Bug: chromium:1334484
      Change-Id: I711913df96c8acc786ad4de28de804d2f90e1847
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3695353Reviewed-by: 's avatarKim-Anh Tran <kimanh@chromium.org>
      Commit-Queue: Simon Zünd <szuend@chromium.org>
      Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#81097}
      79db56f1
  20. 09 Jun, 2022 2 commits
  21. 08 Jun, 2022 4 commits
  22. 07 Jun, 2022 1 commit
  23. 03 Jun, 2022 1 commit
  24. 02 Jun, 2022 3 commits
  25. 01 Jun, 2022 2 commits
  26. 30 May, 2022 1 commit