Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(6)

Unified Diff: include/gpu/GrFragmentProcessor.h

Issue 851143003: Remove willReadDst from GrFragmentProcessor. (Closed) Base URL: https://skia.googlesource.com/skia.git@xferXP
Patch Set: Rebase Created 5 years, 11 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:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | include/gpu/GrXferProcessor.h » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: include/gpu/GrFragmentProcessor.h
diff --git a/include/gpu/GrFragmentProcessor.h b/include/gpu/GrFragmentProcessor.h
index 341b3fb33823743caed28bb7fbeb249e6a9d2223..8ebc94e91d2e403b05e06fe28e081bbe2d1b888d 100644
--- a/include/gpu/GrFragmentProcessor.h
+++ b/include/gpu/GrFragmentProcessor.h
@@ -24,7 +24,6 @@ class GrFragmentProcessor : public GrProcessor {
public:
GrFragmentProcessor()
: INHERITED()
- , fWillReadDstColor(false)
, fWillUseInputColor(true)
, fUsesLocalCoords(false) {}
@@ -51,9 +50,6 @@ public:
return fCoordTransforms;
}
- /** Will this prceossor read the destination pixel value? */
- bool willReadDstColor() const { return fWillReadDstColor; }
-
/** Will this prceossor read the source color value? */
bool willUseInputColor() const { return fWillUseInputColor; }
@@ -106,13 +102,6 @@ protected:
void addCoordTransform(const GrCoordTransform*);
/**
- * If the prceossor subclass will read the destination pixel value then it must call this
- * function from its constructor. Otherwise, when its generated backend-specific prceossor class
- * attempts to generate code that reads the destination pixel it will fail.
- */
- void setWillReadDstColor() { fWillReadDstColor = true; }
-
- /**
* If the prceossor will generate a result that does not depend on the input color value then it
* must call this function from its constructor. Otherwise, when its generated backend-specific
* code might fail during variable binding due to unused variables.
@@ -136,7 +125,6 @@ private:
bool hasSameTransforms(const GrFragmentProcessor&) const;
SkSTArray<4, const GrCoordTransform*, true> fCoordTransforms;
- bool fWillReadDstColor;
bool fWillUseInputColor;
bool fUsesLocalCoords;
« no previous file with comments | « no previous file | include/gpu/GrXferProcessor.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698