Implement support for mixed sampled render targets

src/gpu/GrContext.cpp

Index: src/gpu/GrContext.cpp
diff --git a/src/gpu/GrContext.cpp b/src/gpu/GrContext.cpp
index 78f29e73bc713d773ce27ce94164244316b83c25..ed4709df64274a7d2c454421e08d8fd9c9ecd4bc 100755
--- a/src/gpu/GrContext.cpp
+++ b/src/gpu/GrContext.cpp
@@ -218,7 +218,8 @@ GrTextContext* GrContext::createTextContext(GrRenderTarget* renderTarget,
                                             const SkDeviceProperties&
                                             leakyProperties,
                                             bool enableDistanceFieldFonts) {
-    if (fGpu->caps()->pathRenderingSupport() && renderTarget->isMultisampled()) {
+    if (fGpu->caps()->pathRenderingSupport() &&
+        renderTarget->isMultisampled(GrRenderTarget::kStencilBuffer_PipelineStage)) {
         GrStencilBuffer* sb = renderTarget->renderTargetPriv().attachStencilBuffer();

[bsalomon, 2015/04/01 13:15:35]

I'm not sure that this is necessary anymore. We should just attach a stencil
buffer when it is first used. Here is a place where it seems a bit awkward that
the msaa-ness of the stencil is property of the render target, since at this
point the rt might not even have a stencil buffer yet.

[Chris Dalton, 2015/04/01 20:34:17]

So I don't think it has to be awkward. While it is true that the OpenGL fbo
might not have a stencil buffer attached yet, that is just an implementation
detail. For our purposes, the RT object *does* have a stencil, and that stencil
buffer *is* multisampled, and if we ever try to use it, it will be there.
(That's my understanding.. correct me if I'm wrong.) I feel that is definitely a
property of our RT object though. Just because at the implementation level the
stencil buffer is allocated lazily, I don't think it changes the intrinsic
properties of the abstract RT object.

         if (sb) {
             return GrStencilAndCoverTextContext::Create(this, leakyProperties);