Implement support for mixed sampled render targets

src/gpu/GrStencilAndCoverTextContext.cpp

Index: src/gpu/GrStencilAndCoverTextContext.cpp
diff --git a/src/gpu/GrStencilAndCoverTextContext.cpp b/src/gpu/GrStencilAndCoverTextContext.cpp
index 4b121da905d34cfcf1f590511c0a39489faeb9df..f3fd90b827c5976bdf53002de45fd6f538be06f8 100644
--- a/src/gpu/GrStencilAndCoverTextContext.cpp
+++ b/src/gpu/GrStencilAndCoverTextContext.cpp
@@ -358,6 +358,7 @@ void GrStencilAndCoverTextContext::init(GrRenderTarget* rt,
     fStateRestore.set(&fPipelineBuilder);
 
     fPipelineBuilder.setFromPaint(fPaint, fRenderTarget, fClip);
+    fPipelineBuilder.enableState(GrPipelineBuilder::kHWAntialias_StateBit);

[Chris Dalton, 2015/03/16 19:31:24]

I forgot before that we technically should only enable MSAA if the paint wants
it.

  fPaint.setState(GrPipelineBuilder::kHWAntialias_StateBit,
fPaint.isAntiAlias());

But on second thought, maybe we should modify GrPipelineBuilder::setFromPaint
instead? That way we wouldn't have to turn around and enable kHWAntialias right
after setFromPaint disables it.

  setFromPaint(const GrPaint&, bool rtIsMultisampled, const GrClip&)
  setFromPaint(const GrPaint&, GrRenderTarget* rt, const GrClip&, GrSampleConfig
= kUnified)

I'm not convinced whether it would be better or worse to modify setFromPaint
something like the above. What do you think?

 
     GR_STATIC_CONST_SAME_STENCIL(kStencilPass,
                                  kZero_StencilOp,