|
|
Chromium Code Reviews|
Created:
3 years, 10 months ago by Geoff Lang Modified:
3 years, 10 months ago Reviewers:
Zhenyao Mo CC:
chromium-reviews, piman+watch_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionCheck for some extensions before calling potentially NULL GL entry points.
Some extensions are exposed by the command buffer unconditionally, add
some tracking of which extensions are natively supported and call the
correct entry point.
BUG=602737
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/2689203002
Cr-Commit-Position: refs/heads/master@{#450816}
Committed: https://chromium.googlesource.com/chromium/src/+/0526716fe414eef61b0c151affd57b6f3bb6c96f
Patch Set 1 #
Total comments: 2
Patch Set 2 : refactor feature_info a bit #Patch Set 3 : Fix compile #Patch Set 4 : Revert discard_framebuffer functional change #
Messages
Total messages: 31 (22 generated)
Description was changed from ========== Check for some extensions before calling potentially NULL GL entry points. Some extensions are exposed by the command buffer unconditionally, add some tracking of which extensions are natively supported and call the correct entry point. BUG=602737 ========== to ========== Check for some extensions before calling potentially NULL GL entry points. Some extensions are exposed by the command buffer unconditionally, add some tracking of which extensions are natively supported and call the correct entry point. BUG=602737 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 ==========
The CQ bit was checked by geofflang@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
geofflang@chromium.org changed reviewers: + zmo@chromium.org
PTAL
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... File gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h (right): https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h:388: bool has_chromium_copy_compressed_texture_; Can we consolidate these to FeatureInfo? It seems to be a better place for these caps.
https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... File gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h (right): https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h:388: bool has_chromium_copy_compressed_texture_; On 2017/02/13 18:12:08, Zhenyao Mo wrote: > Can we consolidate these to FeatureInfo? It seems to be a better place for these > caps. I tried but these features are enabled sometimes when the extension doesn't exist. For example, the FeatureInfo says that ext_discard_framebuffer is present when the native extension exists or it's on es3 because it knows it can be emulated. I need to do a little extra tracking to know which native function to call.
On 2017/02/13 19:53:06, Geoff Lang wrote: > https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... > File gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h (right): > > https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... > gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h:388: bool > has_chromium_copy_compressed_texture_; > On 2017/02/13 18:12:08, Zhenyao Mo wrote: > > Can we consolidate these to FeatureInfo? It seems to be a better place for > these > > caps. > > I tried but these features are enabled sometimes when the extension doesn't > exist. For example, the FeatureInfo says that ext_discard_framebuffer is > present when the native extension exists or it's on es3 because it knows it can > be emulated. I need to do a little extra tracking to know which native function > to call. I see. Then I think we should fix the messiness in FeatureInfo to move forward. For example, FeatureInfo.ext_discard_framebuffer should only be true of the native extension exists, and the command buffer should check FeatureInfo.ext_discard_framebuffer or es3. Sorry to put this burden on you.
The CQ bit was checked by geofflang@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2017/02/13 19:58:15, Zhenyao Mo wrote: > On 2017/02/13 19:53:06, Geoff Lang wrote: > > > https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... > > File gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h (right): > > > > > https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... > > gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h:388: bool > > has_chromium_copy_compressed_texture_; > > On 2017/02/13 18:12:08, Zhenyao Mo wrote: > > > Can we consolidate these to FeatureInfo? It seems to be a better place for > > these > > > caps. > > > > I tried but these features are enabled sometimes when the extension doesn't > > exist. For example, the FeatureInfo says that ext_discard_framebuffer is > > present when the native extension exists or it's on es3 because it knows it > can > > be emulated. I need to do a little extra tracking to know which native > function > > to call. > > I see. Then I think we should fix the messiness in FeatureInfo to move forward. > > For example, FeatureInfo.ext_discard_framebuffer should only be true of the > native extension exists, and the command buffer should check > FeatureInfo.ext_discard_framebuffer or es3. > > Sorry to put this burden on you. Refactored a bit to use feature_info. Only functional change is that GL_EXT_discard_framebuffer is no longer exposed unless there is native support. Is that Ok? For ANGLE, it is always supported.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_android on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)
The CQ bit was checked by geofflang@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...)
The CQ bit was checked by geofflang@chromium.org to run a CQ dry run
On 2017/02/15 18:05:34, Geoff Lang wrote: > On 2017/02/13 19:58:15, Zhenyao Mo wrote: > > On 2017/02/13 19:53:06, Geoff Lang wrote: > > > > > > https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... > > > File gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h (right): > > > > > > > > > https://codereview.chromium.org/2689203002/diff/1/gpu/command_buffer/service/... > > > gpu/command_buffer/service/gles2_cmd_decoder_passthrough.h:388: bool > > > has_chromium_copy_compressed_texture_; > > > On 2017/02/13 18:12:08, Zhenyao Mo wrote: > > > > Can we consolidate these to FeatureInfo? It seems to be a better place for > > > these > > > > caps. > > > > > > I tried but these features are enabled sometimes when the extension doesn't > > > exist. For example, the FeatureInfo says that ext_discard_framebuffer is > > > present when the native extension exists or it's on es3 because it knows it > > can > > > be emulated. I need to do a little extra tracking to know which native > > function > > > to call. > > > > I see. Then I think we should fix the messiness in FeatureInfo to move > forward. > > > > For example, FeatureInfo.ext_discard_framebuffer should only be true of the > > native extension exists, and the command buffer should check > > FeatureInfo.ext_discard_framebuffer or es3. > > > > Sorry to put this burden on you. > > Refactored a bit to use feature_info. Only functional change is that > GL_EXT_discard_framebuffer is no longer exposed unless there is native support. > Is that Ok? For ANGLE, it is always supported. Reverted the functional change to GL_EXT_discard_framebuffer, a bunch of tests had expectations around it. Should be no functional changes now.
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by geofflang@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 60001, "attempt_start_ts": 1487193785381630,
"parent_rev": "32e074e42207bf161510aba4c4b5539d0818d2f1", "commit_rev":
"0526716fe414eef61b0c151affd57b6f3bb6c96f"}
CQ is committing da patch.
Bot data: {"patchset_id": 60001, "attempt_start_ts": 1487193785381630,
"parent_rev": "32e074e42207bf161510aba4c4b5539d0818d2f1", "commit_rev":
"0526716fe414eef61b0c151affd57b6f3bb6c96f"}
Message was sent while issue was closed.
Description was changed from ========== Check for some extensions before calling potentially NULL GL entry points. Some extensions are exposed by the command buffer unconditionally, add some tracking of which extensions are natively supported and call the correct entry point. BUG=602737 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 ========== to ========== Check for some extensions before calling potentially NULL GL entry points. Some extensions are exposed by the command buffer unconditionally, add some tracking of which extensions are natively supported and call the correct entry point. BUG=602737 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/2689203002 Cr-Commit-Position: refs/heads/master@{#450816} Committed: https://chromium.googlesource.com/chromium/src/+/0526716fe414eef61b0c151affd5... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as https://chromium.googlesource.com/chromium/src/+/0526716fe414eef61b0c151affd5... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
