Skip to content

V
V8
Switch branch/tag
  1. 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
  3. 09 Jun, 2022 2 commits
  5. 08 Jun, 2022 4 commits
  7. 07 Jun, 2022 1 commit
  9. 03 Jun, 2022 1 commit
  11. 02 Jun, 2022 3 commits
  13. 01 Jun, 2022 2 commits
  15. 30 May, 2022 1 commit
  17. 25 May, 2022 1 commit
  19. 24 May, 2022 2 commits
  21. 23 May, 2022 1 commit
  23. 20 May, 2022 5 commits
  25. 19 May, 2022 1 commit
  27. 18 May, 2022 3 commits
  29. 17 May, 2022 3 commits
  31. 13 May, 2022 3 commits
  33. 10 May, 2022 1 commit
  35. 09 May, 2022 1 commit
    • Camillo Bruni's avatar
      [flags] Introduce --max-opt · 40136c1b
      Camillo Bruni authored 
      There are currently several flags to tune V8's optimisation level:
  --sparkplug, --maglev, --opt

This CL tries to make this simpler by introducing yet another flag.
--max-opt limits the maximum optimisation tier and avoids the common
error to mistake --no-opt with no dynamic optimisations.

Settings:
  --max-opt=999 Allow all optimisations, default configuration.
                Any number > 3 will do, as long as no other tier will be
                added.
  --max-opt=0   Allow only ignition
  --max-opt=1   Allow up to sparkplug
  --max-opt=2   Allow up to maglev
  --max-opt=3   Allow up to turbofan

Bug: v8:12825
Change-Id: Iff9a0fcccdf05e9770168053a1430303613a7299
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3605816
Commit-Queue: Camillo Bruni <cbruni@chromium.org>
Reviewed-by: 's avatarJakob Linke <jgruber@chromium.org>
Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#80418}
      40136c1b
  37. 05 May, 2022 1 commit
  39. 04 May, 2022 1 commit
  41. 03 May, 2022 1 commit