client-side behavior for out-of-bounds vertex attribute accesses depends on driver details |
|||
Issue descriptionForked from item 1 of https://bugs.chromium.org/p/chromium/issues/detail?id=738228#c7 Basically we use the driver's view of which attributes are used or not (from glGetActiveAttrib) to decide whether to apply out-of-bounds checks or not. Different drivers apply different optimizations which can result in different results for which attributes are used. I.e. the same draw call can go through when running on one driver but fail when running on another one. The solution would be to use a consistent view of attribute usage, for example coming from the translator.
,
Jul 9
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
,
Jul 9
|
|||
►
Sign in to add a comment |
|||
Comment 1 by piman@chromium.org
, Jul 7 2017