- 09 Jan, 2020 1 commit
-
-
Clemens Backes authored
This is a cleanup to remove unneeded flags after these changes (in https://crrev.com/c/1988548): * --future does not imply --wasm-tier-up any more, and * --wasm-tier-up does not imply --liftoff any more. Instead, now * --wasm-tier-up is enabled by default, * --wasm-tier-up has no effect if --liftoff is not set, and * --future implies --liftoff. R=ahaas@chromium.org Bug: chromium:1040061 Change-Id: I5d04ee1f1d84ddcd0654df0e0a4c6298f80aee9e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1993280Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#65666}
-
- 12 Nov, 2019 1 commit
-
-
Michael Achenbach authored
This allows the tests to continue running on the gc fuzzers while staying compatible with the --force-slow-path flag being passed randomly. When run in slow_path variants these tests are no-ops, but that's negligible as the tests are also fast without slow_path. Change-Id: I461c47b669b163e1e1594ea1a941f63e90f2221e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1910947Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#64914}
-
- 08 Oct, 2019 1 commit
-
-
Clemens Backes authored
This brings our constants back in line with the changed spec text. We already use kExprTableGet and kExprTableSet, but for locals and globals we still use the old wording. This renaming is mostly mechanical. PS1 was created using: ag -l 'kExpr(Get|Set|Tee)Local' src test | \ xargs -L1 sed -E 's/kExpr(Get|Set|Tee)Local\b/kExprLocal\1/g' -i PS2 contains manual fixes. R=mstarzinger@chromium.org Bug: v8:9810 Change-Id: I1617f1b2a100685a3bf56218e76845a9481959c5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1847354Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#64161}
-
- 24 Sep, 2019 1 commit
-
-
Michael Starzinger authored
This reduces the number of label indices accepted by {br_table} from the full function body size to specifically 65520 labels. Note that TurboFan already had a similar limitation on switches, but caused a crash during compilation up until now. This change just makes the limit explicit and avoids the crash during compilation. R=clemensh@chromium.org TEST=mjsunit/regress/wasm/regress-9759 BUG=v8:9759 Change-Id: I3a9a4406b19a7f98fc36707b3b946be846170a15 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1821457 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Clemens Backes [né Hammacher] <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63944}
-