Fix inconsistencies in CHROMIUM_sync_point.txt.

gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt

 Name
 
     CHROMIUM_sync_point
 
 Name Strings
 
     GL_CHROMIUM_sync_point
 
 Version
 
@@ skipping 45 matching lines @@
         void GenSyncTokenCHROMIUM(uint64 fence_sync, GLbyte *sync_token)
 
     converts <fence_sync> which is only visible to the current context to a
     sync token which may be waited upon by any contexts on the same server.
     The <fence_sync> command must be flushed before this function may be
     called, otherwise an INVALID_OPERATION error is generated. The generated
     <sync_token> must be generated on the same context as when
     InsertFenceSyncCHROMIUM was called. The <sync_token> can be passed and
     used by any context on the same server, including other context groups.
 
-    <sync_token> returns a GL_SYNC_POINT_SIZE_CHROMIUM byte sized name.
+    <sync_token> returns a GL_SYNC_TOKEN_SIZE_CHROMIUM byte sized name.
 
     The command
 
         void GenUnverifiedSyncTokenCHROMIUM(uint64 fence_sync,
                                             GLbyte *sync_token)
 
     converts <fence_sync>, which is only visible to the current context, to a
     sync token, which may be waited upon by a context which only needs flush
     order guarantee with respect to the fence sync context. For example, if
     the two contexts are on the same channel but on different streams, flush
     order guarantee is enough to guarantee that the server will receive the
     release command before the wait command. The <fence_sync> command must be
     flushed before this function may be called, otherwise an INVALID_OPERATION
     error is generated. The generated <sync_token> must be generated on the
     same context as when InsertFenceSyncCHROMIUM was called.
 
     The command
 
         void WaitSyncTokenCHROMIUM(const GLbyte *sync_token)
 
     causes the current context to stop submitting commands until the specified
     fence sync becomes signaled. This is implemented as a server-side wait.
     <sync_token> is a sync token generated by GenSyncPointCHROMIUM. If

[David Yen, 2015/11/20 17:51:36]

s/GenSyncPointCHROMIUM/GenSyncTokenCHROMIUM

     <sync_token> was generated by GenUnverifiedSyncTokenCHROMIUM and the
     corresponding fence sync context required more than just flush ordering
     to guarantee synchronization, a INVALID_OPERATION error is generated. If
     <sync_token> isn't a valid sync token returned by GenSyncPointCHROMIUM or

[David Yen, 2015/11/20 17:51:36]

s/GenSyncPointCHROMIUM/GenSyncTokenCHROMIUM

     GenUnverifiedSyncTokenCHROMIUM, the result is undefined.
 
 New Tokens
 
     The size of a sync token name in bytes.
 
         GL_SYNC_TOKEN_SIZE_CHROMIUM                        24
 
 Errors
 
     INVALID_VALUE is generated if the <fence_sync> parameter of
     GenSyncPointCHROMIUM is not a valid local fence sync name.

[David Yen, 2015/11/20 17:51:36]

s/GenSyncPointCHROMIUM/GenSyncTokenCHROMIUM

 
     INVALID_OPERATION is generated if the <fence_sync> parameter of
     GenSyncPointCHROMIUM has not been flushed to the server.

[David Yen, 2015/11/20 17:51:36]

s/GenSyncPointCHROMIUM/GenSyncTokenCHROMIUM

 
     INVALID_OPERATION is generated if the <sync_token> parameter of
     WaitSyncTokenCHROMIUM was generated using GenUnverifiedSyncTokenCHROMIUM,
     but the two contexts must be synchronized with more than just flush order.
 
 New State
 
     None.
 
 Revision History
 
     2/25/2013    Documented the extension
 
     9/8/2015     Modified functions InsertFenceSyncCHROMIUM,
     GenSyncTokenCHROMIUM, and WaitSyncTokenCHROMIUM.
 
     10/12/2015   Added function GenUnverifiedSyncTokenCHROMIUM.