Implemented new fence syncs which replaces the old sync points.

gpu/command_buffer/build_gles2_cmd_buffer.py

Index: gpu/command_buffer/build_gles2_cmd_buffer.py
diff --git a/gpu/command_buffer/build_gles2_cmd_buffer.py b/gpu/command_buffer/build_gles2_cmd_buffer.py
index 370156e38b88445513523d5e06a66ef937b80c03..d294322ee3281e61408b2f3452718ed384a1a2bd 100755
--- a/gpu/command_buffer/build_gles2_cmd_buffer.py
+++ b/gpu/command_buffer/build_gles2_cmd_buffer.py
@@ -4061,6 +4061,28 @@ _FUNCTION_INFO = {
     'chromium': True,
     'trace_level': 1,
   },
+  'InsertFenceSyncCHROMIUM': {
+    'type': 'Custom',

[piman, 2015/09/10 23:55:32]

I think this one doesn't have to be Custom, because you don't need specific
validation, and you don't change the return value. So if you remove 'type':
'Custom' and implement DoInsertFenceSyncCHROMIUM instead of
HandleInsertFenceSyncCHROMIUM, you leverage more of the autogen.

[David Yen, 2015/09/23 18:30:34]

The 'cmd_args' modification doesn't seem to work without type 'Custom'. Perhaps
it is a bug? I'll leave it as type custom for now.

+    'impl_func': False,
+    'cmd_args': 'GLuint release_count',
+    'extension': "CHROMIUM_sync_point",
+    'chromium': True,
+    'trace_level': 1,
+  },
+  'GenSyncTokenCHROMIUM': {
+    'type': 'Custom',
+    'impl_func': False,
+    'extension': "CHROMIUM_sync_point",
+    'chromium': True,
+  },
+  'WaitSyncTokenCHROMIUM': {
+    'type': 'Custom',
+    'impl_func': False,
+    'cmd_args': 'GLint channel_id, GLuint routing_id, GLuint release_count',
+    'client_test': False,
+    'extension': "CHROMIUM_sync_point",
+    'chromium': True,
+  },
   'DiscardBackbufferCHROMIUM': {
     'type': 'Custom',
     'impl_func': True,