diff options
| author | vmpstr@chromium.org <vmpstr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-16 17:16:46 +0000 |
|---|---|---|
| committer | vmpstr@chromium.org <vmpstr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-16 17:16:46 +0000 |
| commit | c3c977adc859c5b385dd9a362c57d5bf3a202275 (patch) | |
| tree | 162b8ab41adc37013567afe815db2d1bfe818065 /cc/test/fake_picture_layer_tiling_client.cc | |
| parent | 81bf94f418cf0a6868aaf89733dd3ad983181547 (diff) | |
| download | chromium_src-c3c977adc859c5b385dd9a362c57d5bf3a202275.zip chromium_src-c3c977adc859c5b385dd9a362c57d5bf3a202275.tar.gz chromium_src-c3c977adc859c5b385dd9a362c57d5bf3a202275.tar.bz2 | |
cc: Remove predictor benchmark
The predictor benchmark is currently not correct.
However, it's also not used. It's not a part of
telemetry, or UMA. I'd like to remove it in hopes
of cleaning up the code. If we do want this measurement
I propose we find a good spot for it so that it doesn't
add too much code complexity.
BUG=240500
Review URL: https://chromiumcodereview.appspot.com/14587011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200557 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/test/fake_picture_layer_tiling_client.cc')
| -rw-r--r-- | cc/test/fake_picture_layer_tiling_client.cc | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/cc/test/fake_picture_layer_tiling_client.cc b/cc/test/fake_picture_layer_tiling_client.cc index e50d4e5..77c902b 100644 --- a/cc/test/fake_picture_layer_tiling_client.cc +++ b/cc/test/fake_picture_layer_tiling_client.cc @@ -27,7 +27,6 @@ FakePictureLayerTilingClient::FakePictureLayerTilingClient() NULL, 1, false, - false, &stats_instrumentation_), pile_(new FakeInfinitePicturePileImpl()), twin_tiling_(NULL), |