-
Clemens Hammacher authored
In order to test that we don't repeatedly go through the WasmCompileLazy runtime function, add a flag to the LazyCompilationOrchestrator to "freeze" it, i.e. disallow any further lazy compilation. In tests, use this flag to first call a method, then freeze lazy compilation, then call the method again to assert that no further lazy compilation is triggered. This test currently fails with --wasm-jit-to-native, so disable it for that variant. R=titzer@chromium.org CC=mtrofin@chromium.org Bug: v8:7140, chromium:788441, v8:5991 Change-Id: I18a40d302c24041740d8a54351d06ed968f4beec Reviewed-on: https://chromium-review.googlesource.com/796430Reviewed-by: Mircea Trofin <mtrofin@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#49734}
bb64e34f