aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/core/SkRasterPipeline.h
diff options
context:
space:
mode:
authorGravatar Mike Klein <mtklein@chromium.org>2017-06-05 06:32:21 -0400
committerGravatar Skia Commit-Bot <skia-commit-bot@chromium.org>2017-06-05 13:46:40 +0000
commit9beafc41afa3c78ffa12649dcde73628c277da9c (patch)
treef55d4428c25e412f78d8bfee3d321809f7826702 /src/core/SkRasterPipeline.h
parent34d10d734c883758576f3473c5ac38be20c1e99f (diff)
have start_pipeline() return limit again
This is spooky. I don't quite yet understand why, but this makes things much faster. Performance regressed across the board when we no longer needed the value and changed it to return void: https://perf.skia.org/e/?begin=1496176469&keys=6994&xbaroffset=28513 You can see similar regressions following this Chromium bug link. BUG=chromium:729237 Change-Id: I68371b0456014f909acf819aca52aa4f4f187460 Reviewed-on: https://skia-review.googlesource.com/18580 Reviewed-by: Herb Derby <herb@google.com> Reviewed-by: Mike Reed <reed@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
Diffstat (limited to 'src/core/SkRasterPipeline.h')
-rw-r--r--src/core/SkRasterPipeline.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/core/SkRasterPipeline.h b/src/core/SkRasterPipeline.h
index bd54e3f4df..920f6c9351 100644
--- a/src/core/SkRasterPipeline.h
+++ b/src/core/SkRasterPipeline.h
@@ -149,7 +149,7 @@ public:
bool empty() const { return fStages == nullptr; }
private:
- using StartPipelineFn = void(size_t,size_t,size_t,void**,const SkJumper_constants*);
+ using StartPipelineFn = size_t(size_t,size_t,size_t,void**,const SkJumper_constants*);
struct StageList {
StageList* prev;