tree 17cb903e99494ccd163f8a73293277f5bf4ede2d
parent f3d5d44ec9b77d070b6aeaf7c16c504a212ad522
author Greg Daniel <egdaniel@google.com> 1586364771 -0400
committer Skia Commit-Bot <skia-commit-bot@chromium.org> 1586367016 +0000

Update gpu flush semaphore contract.

From my scanning of clients this should not change how any of our main
users interact with semaphores. The biggest change here is that we don't
give up on submitted all the semaphores if a creation fails. We just
submit the semaphores we do have. It also makes it explicit that the
client is responsible for deleting any initialized semaphore regardless
if we were able to submit the semaphores or not or if the semaphore was
wrapped or created by Skia.

The motivation for this change is to more align the current API with
how things will work when we separate flushing and submit into different
calls.

Bug: skia:10118
Change-Id: I3e8b5d3a9852ddb2b5dc972fee21bf46ded7a36f
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/282265
Commit-Queue: Greg Daniel <egdaniel@google.com>
Reviewed-by: Brian Salomon <bsalomon@google.com>