Commit 4c88e38e authored by Jakob Gruber's avatar Jakob Gruber Committed by Commit Bot

[jitless] Clarify flag incompatibility

The --jitless and --interpreted-frames-native-stack flags are
incompatible since the latter requires code generation while the
former prohibits code generation.

Bug: v8:9619
Change-Id: Ic954724edd6a2d28e1bf2f6a79649f86e812abcf
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1758312
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Commit-Queue: Georg Neis <neis@chromium.org>
Auto-Submit: Jakob Gruber <jgruber@chromium.org>
Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#63235}
parent 0dc1f68c
......@@ -90,6 +90,13 @@ void V8::InitializeOncePerProcessImpl() {
FLAG_expose_wasm = false;
}
// The --jitless and --interpreted-frames-native-stack flags are incompatible
// since the latter requires code generation while the former prohibits code
// generation.
CHECK_WITH_MSG(!FLAG_interpreted_frames_native_stack || !FLAG_jitless,
"The --jitless and --interpreted-frames-native-stack flags "
"are incompatible.");
base::OS::Initialize(FLAG_hard_abort, FLAG_gc_fake_mmap);
if (FLAG_random_seed) SetRandomMmapSeed(FLAG_random_seed);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment