377888f565
By applying the same special-case that the Torque builtin already has to the runtime function. This is a quick fix pending discussion what the right long-term solution should be. Bug: v8:13523 Change-Id: I5303d5ac598d00189f7eb2d9d78b81ad11b919b3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4075527 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> Cr-Commit-Position: refs/heads/main@{#84654}
12 lines
515 B
JavaScript
12 lines
515 B
JavaScript
// Copyright 2022 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
// Flags: --experimental-wasm-gc --allow-natives-syntax
|
|
|
|
// The implementation of Promises currently takes a different path (a C++
|
|
// runtime function instead of a Torque builtin) when the debugger is
|
|
// enabled, so exercise that path in this variant of the test.
|
|
d8.debugger.enable();
|
|
d8.file.execute('test/mjsunit/wasm/gc-js-interop-async.js');
|