aboutsummaryrefslogtreecommitdiffhomepage
path: root/src
diff options
context:
space:
mode:
authorGravatar Mike Klein <mtklein@chromium.org>2017-12-22 07:55:15 -0500
committerGravatar Skia Commit-Bot <skia-commit-bot@chromium.org>2017-12-22 14:22:25 +0000
commit03a527c718edc3b39331437822f7131aec71ed0b (patch)
tree2375aba826e68d176b5443273c43eb6aa572834c /src
parent7461a4abe06ffdfbb62a479a71b14895a637bba9 (diff)
Remove another stray pair of clamps.
This clamping should not be necessary now that SkRasterPipeline is more robust to out of gamut values. Change-Id: I17f9af8ccd3d837617a3ed864af1e87e77605cf5 Reviewed-on: https://skia-review.googlesource.com/89160 Reviewed-by: Brian Osman <brianosman@google.com> Commit-Queue: Mike Klein <mtklein@chromium.org>
Diffstat (limited to 'src')
-rw-r--r--src/core/SkDraw_vertices.cpp6
1 files changed, 0 insertions, 6 deletions
diff --git a/src/core/SkDraw_vertices.cpp b/src/core/SkDraw_vertices.cpp
index 52d2a6cd48..69bcff41b2 100644
--- a/src/core/SkDraw_vertices.cpp
+++ b/src/core/SkDraw_vertices.cpp
@@ -89,12 +89,6 @@ protected:
bool onAppendStages(const StageRec& rec) const override {
rec.fPipeline->append_seed_shader();
rec.fPipeline->append(SkRasterPipeline::matrix_4x3, &fM43);
- // In theory we should never need to clamp. However, either due to imprecision in our
- // matrix43, or the scan converter passing us pixel centers that in fact are not within
- // the triangle, we do see occasional (slightly) out-of-range values, so we add these
- // clamp stages. It would be nice to find a way to detect when these are not needed.
- rec.fPipeline->append(SkRasterPipeline::clamp_0);
- rec.fPipeline->append(SkRasterPipeline::clamp_a);
return true;
}