[windows] Fix linker issue

R=clemensh@chromium.org
bug: v8:8275

Change-Id: I4f0beb7064e1a87691e02890b5f96160b1b6c37a
Reviewed-on: https://chromium-review.googlesource.com/c/1268157Reviewed-by: Clemens Hammacher <clemensh@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56448}

src/base/bounded-page-allocator.cc

@@ -19,6 +19,12 @@ BoundedPageAllocator::BoundedPageAllocator(v8::PageAllocator* page_allocator,
   CHECK(IsAligned(allocate_page_size_, commit_page_size_));
 }
 
+BoundedPageAllocator::Address BoundedPageAllocator::begin() const {
+  return region_allocator_.begin();
+}
+
+size_t BoundedPageAllocator::size() const { return region_allocator_.size(); }
+
 void* BoundedPageAllocator::AllocatePages(void* hint, size_t size,
                                           size_t alignment,
                                           PageAllocator::Permission access) {

src/base/bounded-page-allocator.h

@@ -31,8 +31,9 @@ class V8_BASE_EXPORT BoundedPageAllocator : public v8::PageAllocator {
                        size_t size, size_t allocate_page_size);
   ~BoundedPageAllocator() override = default;
 
-  Address begin() const { return region_allocator_.begin(); }
-  size_t size() const { return region_allocator_.size(); }
+  // These functions are not inlined to avoid https://crbug.com/v8/8275.
+  Address begin() const;
+  size_t size() const;
 
   // Returns true if given address is in the range controlled by the bounded
   // page allocator instance.