Turn on the kUsePathBoundsForClip_RecordingFlag in bench, gm and tools that use class PictureRender…

Turn on the kUsePathBoundsForClip_RecordingFlag in bench, gm and tools that use class PictureRenderer

Chrome uses this flag for recording to skpicture in order to improve performance.
Therefore, skai benchmarks should run with this flag enabled, and we need 
gm and render_pictures test coverage to validate it.  In gm, the vanilla 
SkPicture test step will still run without the flag to ensure that case still gets test
coverage, while the SkPicture test steps that use rtree and tileGrid will now run with
the flag enabled.
Committed: https://code.google.com/p/skia/source/detail?r=7234

[EricB, 2013-01-15 19:46:19]

LGTM with some style nits

[EricB, 2013-01-15 20:15:19]

Accidentally didn't publish comments...

https://codereview.appspot.com/7111043/diff/1/gm/gmmain.cpp
File gm/gmmain.cpp (right):

https://codereview.appspot.com/7111043/diff/1/gm/gmmain.cpp#newcode620
gm/gmmain.cpp:620: static SkPicture* generate_new_picture(GM* gm, BbhType
bbhType, uint32_t recordFlags, SkScalar scale = SK_Scalar1) {
Nit: line length

https://codereview.appspot.com/7111043/diff/1/gm/gmmain.cpp#newcode633
gm/gmmain.cpp:633: | SkPicture::kUsePathBoundsForClip_RecordingFlag));
This is really hard to read.  Is there a better way to space it?  Maybe
something like this:

recordFlags |= (kNone_BbhType == bbhType) ? 0
    : (SkPicture::kOptimizeForClippedPlayback_RecordingFlag |
       SkPicture::kUsePathBoundsForClip_RecordingFlag));

Or:

if (kNone_BbhType != bbhType) {
    recordFlags |= (SkPicture::kOptimizeForClippedPlayback_RecordingFlag |
                    SkPicture::kUsePathBoundsForClip_RecordingFlag)
}

https://codereview.appspot.com/7111043/diff/1/gm/gmmain.cpp#newcode1412
gm/gmmain.cpp:1412: SkPicture* pict = gmmain.generate_new_picture(gm,
kTileGrid_BbhType,
Nit: space at EOL

[epoger, 2013-01-16 21:06:08]

LGTM