gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt - Issue 621133003: gpu: Don't flush for future sync point generation

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt

Issue 621133003: gpu: Don't flush for future sync point generation (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 6 years, 2 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt

diff --git a/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt b/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt

index bc8665a306494e70d28f3cbe6d38746cb684aeb2..965cb44b0c066306163f84404232be632a42f644 100644

--- a/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt

+++ b/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt

@@ -40,8 +40,8 @@ New Procedures and Functions

uint InsertSyncPointCHROMIUM()

- creates a sync point and inserts it into the stream of commands for the

- current context. The sync point acts as a fence, which is signaled when

+ flushes the stream of commands for the current context and creates and

+ inserts a sync point. The sync point acts as a fence, which is signaled when

previous commands have been submitted to the server, or when the context is

destroyed, whichever happens first. The sync point name is returned. The

sync point is implicitly deleted when it becomes signaled. The sync point