Only use msaa target for blur mask when doAA is true

Only use msaa target for blur mask when doAA is true

BUG=skia:2995
Committed: https://skia.googlesource.com/skia/+/e6efd39a33a9efa5e20c3289384c0e08ef8c9287

[derekf, 2014-10-07 20:29:42]

derekf@osg.samsung.com changed reviewers:
+ bsalomon@google.com, robertphillips@google.com

[derekf, 2014-10-07 20:29:42]

Only use msaa target when actually anti-aliasing...

Should fix blurrects for issue 2995 because doAA is never set during that test,
so it should run exactly as before.

(however, if the doAA==true cases are also incorrect, this won't help...  I
don't see the blur shift here on debian + HD4000)

[bsalomon, 2014-10-07 20:51:17]

lgtm, but can you add the test name to expectations/gm/ignored-tests.txt before
landing?

[derekf, 2014-10-07 21:26:25]

On 2014/10/07 20:51:17, bsalomon wrote:
> lgtm, but can you add the test name to expectations/gm/ignored-tests.txt
before
> landing?

Oops, sorry.

Added all the tests that this could change (ie: any test where create_mask_GPU
is called with doAA == false.)

[derekf, 2014-10-07 21:34:58]

The CQ bit was checked by derekf@osg.samsung.com

[commit-bot: I haz the power, 2014-10-07 21:35:49]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/639523002/20001

[commit-bot: I haz the power, 2014-10-07 21:44:42]

Committed patchset #2 (id:20001) as e6efd39a33a9efa5e20c3289384c0e08ef8c9287