diff options
| author |  Mike Klein <mtklein@chromium.org> | 2018-06-26 11:43:06 -0400 |
|---|---|---|
| committer |  Skia Commit-Bot <skia-commit-bot@chromium.org> | 2018-06-26 19:02:52 +0000 |
| commit | 3785471ff641b7ec4218a32fcf76363b9ac81bab (patch) | |
| tree | 7596487528841f9a6e32c105c909667c54799d72 /src/core/SkBitmapDevice.cpp | |
| parent | 9b6125d046198bff736a509769b51908aaff326a (diff) | |
basic first pass at RGBA F32 support
Draws basically the same as f16.
The existing load_f32, load_f32_dst, and store_f32 stages all had the
same bug that we'd never noticed because dy was always 0 until now.
Change-Id: Ibbd393fa1acc5df414be4cdef0f5a9d11dcccdb3
Reviewed-on: https://skia-review.googlesource.com/137585
Commit-Queue: Mike Klein <mtklein@chromium.org>
Reviewed-by: Brian Osman <brianosman@google.com>
Reviewed-by: Mike Reed <reed@google.com>
Diffstat (limited to 'src/core/SkBitmapDevice.cpp')
| -rw-r--r-- | src/core/SkBitmapDevice.cpp | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/core/SkBitmapDevice.cpp b/src/core/SkBitmapDevice.cpp index 81ff5bae2a..2361468d56 100644 --- a/src/core/SkBitmapDevice.cpp +++ b/src/core/SkBitmapDevice.cpp @@ -210,6 +210,7 @@ static bool valid_for_bitmap_device(const SkImageInfo& info, case kBGRA_8888_SkColorType: case kRGBA_1010102_SkColorType: case kRGBA_F16_SkColorType: + case kRGBA_F32_SkColorType: break; case kGray_8_SkColorType: case kRGB_565_SkColorType: |