From 1871c8c52b2a0804a9261e7e742b034d049ff27f Mon Sep 17 00:00:00 2001 From: Clemens Hammacher Date: Tue, 8 May 2018 12:07:16 +0200 Subject: [PATCH] [wasm] Allow use of full wasm code space On system which required a contiguous code range, we currently limit the committed wasm code space to the heap code space. Since https://crrev.com/c/1044195, this was only 128MB, making bigger benchmarks fail. There is no need to link the two limits, thus just remove that logic. R=titzer@chromium.org Change-Id: Id61f5dd28c96c3d2b7fcd730751285c6fc144bc5 Reviewed-on: https://chromium-review.googlesource.com/1049648 Reviewed-by: Ben Titzer Reviewed-by: Hannes Payer Commit-Queue: Clemens Hammacher Cr-Commit-Position: refs/heads/master@{#53059} --- src/isolate.cc | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/src/isolate.cc b/src/isolate.cc index 0ddff20159..3c66ceb162 100644 --- a/src/isolate.cc +++ b/src/isolate.cc @@ -3007,14 +3007,9 @@ bool Isolate::Init(StartupDeserializer* des) { } // Setup the wasm engine. Currently, there's one per Isolate. - const size_t max_code_size = - kRequiresCodeRange - ? std::min(kMaxWasmCodeMemory, - heap_.memory_allocator()->code_range()->size()) - : kMaxWasmCodeMemory; wasm_engine_.reset(new wasm::WasmEngine( std::unique_ptr(new wasm::WasmCodeManager( - reinterpret_cast(this), max_code_size)))); + reinterpret_cast(this), kMaxWasmCodeMemory)))); wasm_engine_->memory_tracker()->SetAllocationResultHistogram( counters()->wasm_memory_allocation_result()); wasm_engine_->memory_tracker()->SetAddressSpaceUsageHistogram(