Distance field path optimizations and clean up.

Distance field path optimizations and clean up.

Adds the following:
- Use cached geometry processor rather than recreating all the time.
- Use context's quad index buffer.

Committed: https://skia.googlesource.com/skia/+/6d22ecaa71cf4400feebc3438bf0e0dd68179500

[jvanverth1, 2014-10-28 15:51:28]

jvanverth@google.com changed reviewers:
+ bsalomon@google.com, robertphillips@google.com

[robertphillips, 2014-10-28 16:32:04]

lgtm with 2 suggestions

https://codereview.chromium.org/683923002/diff/20001/src/gpu/GrAADistanceFiel...
File src/gpu/GrAADistanceFieldPathRenderer.h (right):

https://codereview.chromium.org/683923002/diff/20001/src/gpu/GrAADistanceFiel...
src/gpu/GrAADistanceFieldPathRenderer.h:62: SkAutoTUnref<GrGeometryProcessor> 
fCachedGeometryProcessor;
// The flags used to create the cached geometry processor ?

https://codereview.chromium.org/683923002/diff/20001/src/gpu/effects/GrDistan...
File src/gpu/effects/GrDistanceFieldTextureEffect.h (right):

https://codereview.chromium.org/683923002/diff/20001/src/gpu/effects/GrDistan...
src/gpu/effects/GrDistanceFieldTextureEffect.h:24: 
0x80 instead of 0xff ?
You could then have some asserts that the invalid bit isn't set.

[jvanverth1, 2014-10-28 18:01:31]

https://codereview.chromium.org/683923002/diff/20001/src/gpu/GrAADistanceFiel...
File src/gpu/GrAADistanceFieldPathRenderer.h (right):

https://codereview.chromium.org/683923002/diff/20001/src/gpu/GrAADistanceFiel...
src/gpu/GrAADistanceFieldPathRenderer.h:62: SkAutoTUnref<GrGeometryProcessor> 
fCachedGeometryProcessor;
On 2014/10/28 16:32:04, robertphillips wrote:
> // The flags used to create the cached geometry processor ?

Done.

https://codereview.chromium.org/683923002/diff/20001/src/gpu/effects/GrDistan...
File src/gpu/effects/GrDistanceFieldTextureEffect.h (right):

https://codereview.chromium.org/683923002/diff/20001/src/gpu/effects/GrDistan...
src/gpu/effects/GrDistanceFieldTextureEffect.h:24: 
On 2014/10/28 16:32:04, robertphillips wrote:
> 0x80 instead of 0xff ?
> You could then have some asserts that the invalid bit isn't set.

Done.

[jvanverth1, 2014-10-28 18:01:35]

The CQ bit was checked by jvanverth@google.com

[commit-bot: I haz the power, 2014-10-28 18:02:34]

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

[commit-bot: I haz the power, 2014-10-28 18:10:57]

Committed patchset #3 (id:40001) as 6d22ecaa71cf4400feebc3438bf0e0dd68179500