glInvalidateFramebuffer(STENCIL) on a depth stencil texture also clears the depth |
||||
Issue descriptionOn platforms supporting glInvalidateFramebuffer of the stencil attachment of a depth_stencil attachment, GLES2DecoderImpl::InvalidateFramebufferImpl sets dirty = true, causing the depth stencil texture to be considered unintialized (both depth and stencil). Then GLES2DecoderImpl::ClearLevel goes ahead and clears both the depth and stencil. This causes failures in deqp/functional/gles3/fboinvalidate/whole.html for drivers supporting glInvalidateFramebuffer. Mo, I'm not sure what is the best way to proceed. Should we make gl.invalidateFramebuffer be a noop for depth_stencil attachment, when only one of the two channels is cleared?
,
Jun 29 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/96c0e3d1ec373deec7d7e50bcbdfa56eebfa5002 commit 96c0e3d1ec373deec7d7e50bcbdfa56eebfa5002 Author: cwallez <cwallez@chromium.org> Date: Wed Jun 29 22:30:38 2016 WebGL CTS update bug ids for deqp/gles3/fboinvalidate/whole BUG=624506 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2108303002 Cr-Commit-Position: refs/heads/master@{#402961} [modify] https://crrev.com/96c0e3d1ec373deec7d7e50bcbdfa56eebfa5002/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
,
Jul 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/af3b3d8bb5281c929bcfd930cb6ebbfa3a5004c9 commit af3b3d8bb5281c929bcfd930cb6ebbfa3a5004c9 Author: qiankun.miao <qiankun.miao@intel.com> Date: Fri Jul 22 21:39:53 2016 Add unittests for InvalidateFramebuffer with DEPTH_STENCIL_ATTACHMENT Unit tests for https://codereview.chromium.org/2149523002/. BUG= 628496 , 624506 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2166923002 Cr-Commit-Position: refs/heads/master@{#407271} [modify] https://crrev.com/af3b3d8bb5281c929bcfd930cb6ebbfa3a5004c9/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py [modify] https://crrev.com/af3b3d8bb5281c929bcfd930cb6ebbfa3a5004c9/gpu/command_buffer/service/framebuffer_manager.cc [modify] https://crrev.com/af3b3d8bb5281c929bcfd930cb6ebbfa3a5004c9/gpu/command_buffer/service/framebuffer_manager.h [modify] https://crrev.com/af3b3d8bb5281c929bcfd930cb6ebbfa3a5004c9/gpu/command_buffer/service/gles2_cmd_decoder.cc [modify] https://crrev.com/af3b3d8bb5281c929bcfd930cb6ebbfa3a5004c9/gpu/command_buffer/service/gles2_cmd_decoder_unittest_framebuffers.cc
,
Jun 20 2017
,
Jun 21 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 21 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by zmo@chromium.org
, Jun 29 2016