Move font loading in gm tests and benches out of constructors

Move font loading in gm tests and benches out of constructors

Constructing the gm tests and benches causes many calls to font loads.
This is visible as profiling samples in fontconfig and freetype on Linux
for all profiling runs of nanobench. This complicates analysis of
test-cases that are suspected of being slow due to font-related issues.

Move the font loading to GM::onOnceBeforeDraw and Benchmark::onPreDraw.
This way the code is not executed if the testcase does not match the
nanobench --match filter. This way the samples in font-related code are
more easy to identify as legitimate occurances caused by the testcase.

This should not cause differences in timings, because:
* Benchmark::preDraw / onPreDraw is defined to be run outside the timer
* GM::runAsBench is not enabled for any of the modified testcases. Also
  nanobench untimed warmup round should run the onOnceBeforeDraw.
  (and there are other GM::runAsBench gms already doing loading in
   onOnceBeforeDraw).

Changes the behavior:
In TextBench:
Before, the test would report two different gms with the same name if
the color emoji font was not loaded successfully.
After, the test always reports all tests as individual names.

Generally:
The errors from loading fonts now print inbetween each testcase, as
opposed to printing during construction phase. Sample output:
( 143/145 MB  1872) 14.7ms	8888 gm  quadclosepathResource /fonts/Funkster.ttf not a valid font.
( 160/160 MB  1831) 575µs	8888 gm  surfacenewResource /fonts/Funkster.ttf not a valid font.
( 163/165 MB  1816) 12.5ms	8888 gm  linepathResource /fonts/Funkster.ttf not a valid font.
( 263/411 MB  1493) 118ms	8888 gm  typefacestyles_kerningResource /fonts/Funkster.ttf not a valid font.
( 374/411 MB  1231) 7.16ms	565 gm  getpostextpathResource /fonts/Funkster.ttf not a valid font.
( 323/411 MB  1179) 4.92ms	565 gm  stringartResource /fonts/Funkster.ttf not a valid font.
( 347/493 MB   917) 191ms	565 gm  patch_gridResource /fonts/Funkster.ttf not a valid font.
( 375/493 MB   857) 23.9ms	gpu gm  clipdrawdrawCannot render path (0)
( 393/493 MB   706) 2.91ms	unit test  ParsePath------ png error IEND: CRC error
( 394/493 MB   584) 166ms	gpu gm  hairmodesResource /fonts/Funkster.ttf not a valid font.
Resource /fonts/Funkster.ttf not a valid font.
Resource /fonts/Funkster.ttf not a valid font.
...

Committed: https://skia.googlesource.com/skia/+/b4a797f3aa8c10387f01cf51a65dd1a8aa5eec9d

[Kimmo Kinnunen, 2015-05-21 06:44:36]

kkinnunen@nvidia.com changed reviewers:
+ mtklein@google.com

[mtklein, 2015-05-21 13:09:25]

The CQ bit was checked by mtklein@google.com

[mtklein, 2015-05-21 13:09:26]

lgtm

https://codereview.chromium.org/1144023002/diff/40001/bench/TextBench.cpp
File bench/TextBench.cpp (right):

https://codereview.chromium.org/1144023002/diff/40001/bench/TextBench.cpp#new...
bench/TextBench.cpp:94: fName.printf("text_%g",
SkScalarToFloat(fPaint.getTextSize()));
Kind of weird that this builds fName in place then returns it, isn't it?  You'd
think either we have no fName field or this just returns fName.c_str() having
already been formatted in the constructor or something.  Odd.

https://codereview.chromium.org/1144023002/diff/40001/gm/typeface.cpp
File gm/typeface.cpp (right):

https://codereview.chromium.org/1144023002/diff/40001/gm/typeface.cpp#newcode168
gm/typeface.cpp:168: memset(fFaces, 0, sizeof(fFaces));
Just FYI, we usually use sk_bzero for this so we don't accidentally mix up where
the pointer, value, and size go.

[commit-bot: I haz the power, 2015-05-21 13:09:33]

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

[commit-bot: I haz the power, 2015-05-21 13:15:33]

Committed patchset #3 (id:40001) as
https://skia.googlesource.com/skia/+/b4a797f3aa8c10387f01cf51a65dd1a8aa5eec9d