diff options
| author | John Reck <jreck@google.com> | 2019-10-04 14:48:27 -0700 |
|---|---|---|
| committer | John Reck <jreck@google.com> | 2019-10-04 14:49:20 -0700 |
| commit | 83161dcd6aa15c7da161b4ae561b06d20edd2510 (patch) | |
| tree | d564507b70019ef9b3905fbd3256f7c2d51948cd /libs/hwui/Android.bp | |
| parent | 781630e4b4d67e0371c133ae64923ede1b989250 (diff) | |
Delete VectorDrawableAtlas
Poking around in a few apps it doesn't appear that
the VectorDrawableAtlas is achieving sufficient
utilization to justify its existence. The potential for
draw call merging doesn't seem warranted for the
RAM cost of the atlas.
Bug: 137853925
Test: builds
Change-Id: Id2419bc6dccb6316636d50c568f8fac75a2d563f
Diffstat (limited to 'libs/hwui/Android.bp')
| -rw-r--r-- | libs/hwui/Android.bp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/libs/hwui/Android.bp b/libs/hwui/Android.bp index ae90f117d448..1bcef7314bbf 100644 --- a/libs/hwui/Android.bp +++ b/libs/hwui/Android.bp @@ -219,7 +219,6 @@ cc_defaults { "pipeline/skia/SkiaPipeline.cpp", "pipeline/skia/SkiaProfileRenderer.cpp", "pipeline/skia/SkiaVulkanPipeline.cpp", - "pipeline/skia/VectorDrawableAtlas.cpp", "pipeline/skia/VkFunctorDrawable.cpp", "pipeline/skia/VkInteropFunctorDrawable.cpp", "renderstate/RenderState.cpp", @@ -345,7 +344,6 @@ cc_test { "tests/unit/ThreadBaseTests.cpp", "tests/unit/TypefaceTests.cpp", "tests/unit/VectorDrawableTests.cpp", - "tests/unit/VectorDrawableAtlasTests.cpp", "tests/unit/WebViewFunctorManagerTests.cpp", ], } |