glGetFragDataLocation works incorrectly on MacOSX |
|||
Issue description
If an output variable is an array, say A[COUNT], it only succeeds with glGetFragDataLocation("A"), but fails with glGetFragDataLocation("A[0]"), etc.
For WebGL2, since array location is sequential and continuous, we can workaround by querying location for "A" and compute the location for each element in the array.
However, ARB_blend_func_extended won't work with this bug.
conformance2/programs/gl-get-frag-data-location.html is added to catch this bug.
,
Aug 16 2016
,
Aug 16 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/712211c39695d69dcda58ce1cc9c63c3c154b1f6 commit 712211c39695d69dcda58ce1cc9c63c3c154b1f6 Author: zmo <zmo@chromium.org> Date: Tue Aug 16 22:16:15 2016 Work around MacOSX driver bug related with glGetFragDataLocation. BUG=638340 TEST=gl_tests R=piman@chromium.org 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/2250803002 Cr-Commit-Position: refs/heads/master@{#412355} [modify] https://crrev.com/712211c39695d69dcda58ce1cc9c63c3c154b1f6/gpu/command_buffer/service/feature_info.cc [modify] https://crrev.com/712211c39695d69dcda58ce1cc9c63c3c154b1f6/gpu/command_buffer/service/program_manager.cc [modify] https://crrev.com/712211c39695d69dcda58ce1cc9c63c3c154b1f6/gpu/config/gpu_driver_bug_list_json.cc [modify] https://crrev.com/712211c39695d69dcda58ce1cc9c63c3c154b1f6/gpu/config/gpu_driver_bug_workaround_type.h
,
Sep 10 2016
Filed as Radar 28235295.
,
Jun 20 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by zmo@chromium.org
, Aug 16 2016