Provides multiple implementations of Android's SkBitmapRegionDecoder

dm/DMSrcSink.h

Index: dm/DMSrcSink.h
diff --git a/dm/DMSrcSink.h b/dm/DMSrcSink.h
index 0aa22a06084fb795b33ee8094e2508b75bb2ca0e..669830f678c2e534fbc15926eb1c379985da9e02 100644
--- a/dm/DMSrcSink.h
+++ b/dm/DMSrcSink.h
@@ -12,6 +12,7 @@
 #include "SkBBHFactory.h"
 #include "SkBBoxHierarchy.h"
 #include "SkBitmap.h"
+#include "SkBitmapRegionDecoder.h"
 #include "SkCanvas.h"
 #include "SkCodec.h"
 #include "SkData.h"
@@ -100,6 +101,27 @@ private:
     skiagm::GMRegistry::Factory fFactory;
 };
 
+class BRDSrc : public Src {

[scroggo, 2015/08/13 16:53:07]

Maybe add a description for what this is for?

[msarett, 2015/08/13 18:10:23]

Done.

+public:
+    enum Mode {
+        kNormal_Mode,

[scroggo, 2015/08/13 16:53:07]

What do these modes mean? Isn't BRD always used for doing subsets?

[msarett, 2015/08/13 18:10:23]

Maybe we don't need both of these tests or these aren't the only interesting
tests?

I think kFullImage_Mode, kDivisor_Mode are more accurate.

[scroggo, 2015/08/28 13:49:43]

The FullImage mode seems weird. Does it show us something unique, interesting,
or analogous to how clients use it? Divisor definitely seems interesting. Or
maybe these should track the uses in your various benchmarks?
Agreed.

+        kSubset_Mode,
+    };
+
+    BRDSrc(Path, SkBitmapRegionDecoder::Strategy, Mode, SkColorType, uint32_t);
+
+    Error draw(SkCanvas*) const override;
+    SkISize size() const override;
+    Name name() const override;
+    bool veto(SinkFlags) const override;
+private:
+    Path                            fPath;
+    SkBitmapRegionDecoder::Strategy fStrategy;
+    Mode                            fMode;
+    SkColorType                     fColorType;
+    uint32_t                        fSampleSize;
+};
+
 class CodecSrc : public Src {
 public:
     enum Mode {