[Tizen] Ensure to check GLES::ShaderImpl when we found GLES:ProgramImpl 70/302070/1
authorEunki, Hong <eunkiki.hong@samsung.com>
Tue, 21 Nov 2023 06:28:04 +0000 (15:28 +0900)
committerEunki, Hong <eunkiki.hong@samsung.com>
Thu, 30 Nov 2023 02:40:23 +0000 (11:40 +0900)
commit650386a7e80c77853ccd5cc833420e2485d62eec
treeadf6c270157b4f6f704dc2e51766c751714ae686
parenta82c47c313a55349351c18243fa6bb2975204920
[Tizen] Ensure to check GLES::ShaderImpl when we found GLES:ProgramImpl

Previously, We only consider 1 Graphis::Shader per 1 shader codes.
But for now, we allow to use multiple Graphics::Shader per 1 shader code,
by cache GLES::ShaderImpl system.

But we check Graphics::Shader pointer when we found cached ProgramImpl for now.

It will make some unneccessary glLinkProgram call when Graphics::Shader cache
miss occured.

To resolve it, let we cache GLES::Shader wrapper instead of Graphics::Shader.
And compare with the pointer of GLES::ShaderImpl.

Change-Id: I0681cb96448c75a7d6841011c49803329ed3116d
Signed-off-by: Eunki, Hong <eunkiki.hong@samsung.com>
automated-tests/src/dali-graphics/utc-Dali-GraphicsProgram.cpp
dali/internal/graphics/gles-impl/gles-graphics-pipeline-cache.cpp
dali/internal/graphics/gles-impl/gles-graphics-pipeline-cache.h
dali/internal/graphics/gles-impl/gles-graphics-shader.cpp