Expose coord transforms from GrPipeline

Expose coord transforms from GrPipeline

BUG=skia:

Committed: https://skia.googlesource.com/skia/+/2fe7923f7e74f901a17afba7609d71a1220bdc60

[joshualitt, 2015-08-05 16:34:43]

joshualitt@google.com changed reviewers:
+ bsalomon@google.com, joshualitt@google.com

[joshualitt, 2015-08-05 16:34:44]

ptal.  Eventually we can go a step farther and always have GrBatch do the coord
transform compare if necessary.

[bsalomon, 2015-08-05 17:22:12]

https://codereview.chromium.org/1275603002/diff/1/include/gpu/GrFragmentProce...
File include/gpu/GrFragmentProcessor.h (right):

https://codereview.chromium.org/1275603002/diff/1/include/gpu/GrFragmentProce...
include/gpu/GrFragmentProcessor.h:87: generate the same shader code. To test for
identical code generation use getGLProcessorKey*/
update comment?

"Coord transforms may be applied either on the GPU or the CPU. When we apply
them on the CPU then the matrices need not agree in order to combine draws.
Therefore we take a param that indicates whether coord transforms should be
compared."

https://codereview.chromium.org/1275603002/diff/1/src/gpu/GrPipeline.cpp
File src/gpu/GrPipeline.cpp (right):

https://codereview.chromium.org/1275603002/diff/1/src/gpu/GrPipeline.cpp#newc...
src/gpu/GrPipeline.cpp:91: const GrFragmentProcessor* fp = fps.processor();
does this all work for the nested case?

[joshualitt, 2015-08-05 17:46:08]

joshualitt@google.com changed reviewers:
+ wangyix@google.com

[joshualitt, 2015-08-05 17:46:21]

https://codereview.chromium.org/1275603002/diff/1/include/gpu/GrFragmentProce...
File include/gpu/GrFragmentProcessor.h (right):

https://codereview.chromium.org/1275603002/diff/1/include/gpu/GrFragmentProce...
include/gpu/GrFragmentProcessor.h:87: generate the same shader code. To test for
identical code generation use getGLProcessorKey*/
On 2015/08/05 17:22:11, bsalomon wrote:
> update comment?
> 
> "Coord transforms may be applied either on the GPU or the CPU. When we apply
> them on the CPU then the matrices need not agree in order to combine draws.
> Therefore we take a param that indicates whether coord transforms should be
> compared."

Acknowledged.

https://codereview.chromium.org/1275603002/diff/1/src/gpu/GrPipeline.cpp
File src/gpu/GrPipeline.cpp (right):

https://codereview.chromium.org/1275603002/diff/1/src/gpu/GrPipeline.cpp#newc...
src/gpu/GrPipeline.cpp:91: const GrFragmentProcessor* fp = fps.processor();
On 2015/08/05 17:22:12, bsalomon wrote:
> does this all work for the nested case?

good catch

[bsalomon, 2015-08-05 18:52:04]

lgtm

[joshualitt, 2015-08-05 18:53:47]

The CQ bit was checked by joshualitt@google.com

[commit-bot: I haz the power, 2015-08-05 18:54:07]

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

[commit-bot: I haz the power, 2015-08-05 19:02:31]

Committed patchset #2 (id:20001) as
https://skia.googlesource.com/skia/+/2fe7923f7e74f901a17afba7609d71a1220bdc60