Start refactoring Windows allocator shim in prep for hooking in generic allocator shim on Windows.

base/allocator/allocator.gyp

Index: base/allocator/allocator.gyp
diff --git a/base/allocator/allocator.gyp b/base/allocator/allocator.gyp
index 674d4d645f79a2b4a7de7d56589c4bacdb479e65..af27c376b4d3e74c911e6076f17c672f76cd0ed9 100644
--- a/base/allocator/allocator.gyp
+++ b/base/allocator/allocator.gyp
@@ -55,6 +55,8 @@
           'sources': [
             'allocator_shim_win.cc',
             'allocator_shim_win.h',
+            'winheap_stubs_win.cc',
+            'winheap_stubs_win.h',
           ],
           'configurations': {
             'Debug_Base': {
@@ -386,6 +388,7 @@
         'buildflag_header_path': 'base/allocator/features.h',
         'buildflag_flags': [
           'USE_EXPERIMENTAL_ALLOCATOR_SHIM=<(use_experimental_allocator_shim)',
+          'ENABLE_WIN_ALLOCATOR_SHIM_TESTS=<(use_experimental_allocator_shim)||<(win_use_allocator_shim)',

[Primiano Tucci (use gerrit), 2016/07/13 17:42:49]

uhm not sure about this part. At very least this should be s/||/or/
But then I am not sure if the right way of spelling this is:
1) 'FLAG=<(a) or <(b)'
2) 'FLAG=<(a or b)'
3) you cannot do this and need to create first a variable two lines above.

You need a gyp-ninja for this :)

[Sigurður Ásgeirsson, 2016/07/13 18:47:45]

I tested the GYP build locally, and the tests run under this condition.

Unfortunately '<(a or b)' does not work, as GYP tries to resolve the variable "a
or b" with poor success. Any whitespace in the expression turns into a newline
in the macro definition. Leave as-is, grit our teeth and wait for GYP to die?

         ],
       },
     },  # 'allocator_features' target.