[wasm] Add guard regions to end of WebAssembly.Memory buffers

src/wasm/wasm-module.h

Index: src/wasm/wasm-module.h
diff --git a/src/wasm/wasm-module.h b/src/wasm/wasm-module.h
index 3ac410476d7c6fc9a6a0752f1b7fccb5016a384d..b460eba524570141cc579c978329662edd755900 100644
--- a/src/wasm/wasm-module.h
+++ b/src/wasm/wasm-module.h
@@ -36,6 +36,11 @@ const uint32_t kWasmVersion = 0x0d;
 const uint8_t kWasmFunctionTypeForm = 0x60;
 const uint8_t kWasmAnyFunctionTypeForm = 0x70;
 
+const uint64_t kWasmMaxHeapOffset =
+    static_cast<uint64_t>(
+        std::numeric_limits<uint32_t>::max())  // maximum base value
+    + std::numeric_limits<uint32_t>::max();    // maximum index value
+
 enum WasmSectionCode {
   kUnknownSectionCode = 0,   // code for unknown sections
   kTypeSectionCode = 1,      // Function signature declarations
@@ -559,6 +564,8 @@ int32_t GetInstanceMemorySize(Isolate* isolate, Handle<JSObject> instance);
 int32_t GrowInstanceMemory(Isolate* isolate, Handle<JSObject> instance,
                            uint32_t pages);
 
+Handle<JSArrayBuffer> NewArrayBuffer(Isolate* isolate, size_t size, bool guard);

[titzer, 2016/11/07 19:54:53]

add_guard_pages?

[Eric Holk, 2016/11/08 23:58:15]

I went with enable_guard_regions based on your other comment.

+
 void UpdateDispatchTables(Isolate* isolate, Handle<FixedArray> dispatch_tables,
                           int index, Handle<JSFunction> js_function);