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

base/allocator/allocator.gyp

 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 {
   'target_defaults': {
     'variables': {
       # This code gets run a lot and debugged rarely, so it should be fast
       # by default. See http://crbug.com/388949.
       'debug_optimize': '2',
@@ skipping 37 matching lines @@
             'VCLinkerTool': {
               'AdditionalOptions': ['/ignore:4006'],
             },
           },
           'include_dirs': [
             '../..',
           ],
           'sources': [
             'allocator_shim_win.cc',
             'allocator_shim_win.h',
+            'winheap_stubs_win.cc',
+            'winheap_stubs_win.h',
           ],
           'configurations': {
             'Debug_Base': {
               'msvs_settings': {
                 'VCCLCompilerTool': {
                   'RuntimeLibrary': '0',
                 },
               },
             },
           },
@@ skipping 311 matching lines @@
     {
       # GN: //base/allocator:features
       # When referenced from a target that might be compiled in the host
       # toolchain, always refer to 'allocator_features#target'.
       'target_name': 'allocator_features',
       'includes': [ '../../build/buildflag_header.gypi' ],
       'variables': {
         '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.
   ],  # targets.
   'conditions': [
     ['use_experimental_allocator_shim==1', {
       'targets': [
         {
           # GN: //base/allocator:unified_allocator_shim
           'target_name': 'unified_allocator_shim',
@@ skipping 42 matching lines @@
                   '-Wl,-wrap,valloc',
                 ],
               },
             }],
           ]
         },  # 'unified_allocator_shim' target.
       ],
     }]
   ],
 }