Added game-like bench marks

Need these to diagnose Chrome-side performance regressions.

The overall lesson is 565 needs a new blitter.

game_rot_partial_aa  8888: cmsecs = 396.24   565: cmsecs = 524.16   GPU: cmsecs =  37.44
game_trans_partial_aa  8888: cmsecs =  60.84   565: cmsecs = 190.32   GPU: cmsecs =  40.56
game_scale_partial_aa  8888: cmsecs = 310.44   565: cmsecs = 458.64   GPU: cmsecs =  43.68
game_rot_full_aa  8888: cmsecs = 280.80   565: cmsecs = 411.84   GPU: cmsecs =  21.84
game_trans_full_aa  8888: cmsecs =  39.00   565: cmsecs = 168.48   GPU: cmsecs =  20.28
game_scale_full_aa  8888: cmsecs = 274.56   565: cmsecs = 432.12   GPU: cmsecs =  21.84

[bsalomon, 2013-05-09 15:50:46]

lgtm w/ some questions

https://codereview.chromium.org/14772019/diff/1/bench/GameBench.cpp
File bench/GameBench.cpp (right):

https://codereview.chromium.org/14772019/diff/1/bench/GameBench.cpp#newcode15
bench/GameBench.cpp:15: // This bench simulates the calls Skia sees from various
HTML5 canvas
Maybe say which ones in case we forget?

https://codereview.chromium.org/14772019/diff/1/bench/GameBench.cpp#newcode19
bench/GameBench.cpp:19: static const unsigned int kNumRects = 5000;
should this be in that macro that sets it to 1 in debug builds?

should these values be private?

[reed1, 2013-05-09 16:04:55]

https://codereview.chromium.org/14772019/diff/1/bench/GameBench.cpp
File bench/GameBench.cpp (right):

https://codereview.chromium.org/14772019/diff/1/bench/GameBench.cpp#newcode58
bench/GameBench.cpp:58: this->makeCheckerboard();
can we do this lazily, so the constructor is light-weight? The tool can rip
through all the benches to get their names, and then only exercise a subset of
them.

[robertphillips, 2013-05-09 18:49:15]

PTAL

https://codereview.chromium.org/14772019/diff/1/bench/GameBench.cpp
File bench/GameBench.cpp (right):

https://codereview.chromium.org/14772019/diff/1/bench/GameBench.cpp#newcode19
bench/GameBench.cpp:19: static const unsigned int kNumRects = 5000;
On 2013/05/09 15:50:46, bsalomon wrote:
> should this be in that macro that sets it to 1 in debug builds?
> 
> should these values be private?

Done.

https://codereview.chromium.org/14772019/diff/1/bench/GameBench.cpp#newcode58
bench/GameBench.cpp:58: this->makeCheckerboard();
On 2013/05/09 16:04:55, reed1 wrote:
> can we do this lazily, so the constructor is light-weight? The tool can rip
> through all the benches to get their names, and then only exercise a subset of
> them.

Done.

[bsalomon, 2013-05-09 18:51:46]

lgtm

[robertphillips, 2013-05-09 19:04:05]

committed as r9078