Make use of VkSemaphores thread safe assuming use of the same VkQueue.

This allows us to re-enable support for multiple GrContexts in
GrBackendTextureImageGenerator.

Bug: skia:
Change-Id: Ifd6ac1ad81cdfbd1fd986467d8beb359399d6588
Reviewed-on: https://skia-review.googlesource.com/98340
Reviewed-by: Brian Osman <brianosman@google.com>
Reviewed-by: Brian Salomon <bsalomon@google.com>
Commit-Queue: Greg Daniel <egdaniel@google.com>

1 files changed, 0 insertions, 11 deletions

diff --git a/src/gpu/GrSemaphore.h b/src/gpu/GrSemaphore.h
index 20556d27ac..fbc5a6df56 100644
--- a/src/gpu/GrSemaphore.h
+++ b/src/gpu/GrSemaphore.h
@@ -13,15 +13,7 @@
 class GrBackendSemaphore;
 class GrGpu;
 
-/*
- * Wrapper around a semaphore object which must be implemented on each backend. This semaphores can
- * at most be signaled once and waited upon once.
- */
 class GrSemaphore : public SkRefCnt {
-public:
-    bool hasSubmittedSignal() const { return fSignaled; }
-    bool hasSubmittedWait() const { return fWaitedOn; }
-
 private:
     // This function should only be used in the case of exporting and importing a GrSemaphore object
     // from one GrContext to another. When exporting, the GrSemaphore should be set to a null GrGpu,
@@ -34,9 +26,6 @@ private:
     // internal semaphore.
     virtual void setBackendSemaphore(GrBackendSemaphore*) const = 0;
 
-    bool fSignaled = false;
-    bool fWaitedOn = false;
-
 protected:
     explicit GrSemaphore(const GrGpu* gpu) : fGpu(gpu) {}