diff options
author | 2016-11-02 14:47:07 -0400 | |
---|---|---|
committer | 2016-11-03 18:22:54 +0000 | |
commit | 6b059bdc40d070fe08a3ff071e45be782297ab08 (patch) | |
tree | 13cee6e84969517baf1cf2e45b25f136448320a8 /tools/skpbench | |
parent | 71d9d84d6cd38b9dc8711849952bb9e668ab33a2 (diff) |
Remove sk_linear_to_srgb_noclamp().
We've just re-noticed this can happen:
1) we have a properly premultiplied linear color;
2) we convert that to sRGB;
3) we convert that back to linear;
4) that color does not appear to be premultiplied.
Removing sk_linear_to_srgb_noclamp(), and thus always clamping to [0,1] here in linear space, does not fix this problem. However, it does help keep it from propagating too badly.
Just double-checked: the older Sk4f pipeline (SkXfermode4f, SkPM4fPriv, etc) already use sk_linear_to_srgb() exclusively, so they're already doing this same clamp.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=4314
Change-Id: I6352eb0ba969eb25674e8441e43bb51e1e1c0df3
Reviewed-on: https://skia-review.googlesource.com/4314
Reviewed-by: Yuqian Li <liyuqian@google.com>
Commit-Queue: Mike Klein <mtklein@chromium.org>
Diffstat (limited to 'tools/skpbench')
0 files changed, 0 insertions, 0 deletions