<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - XCOM: Enemy Unknown Causes lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=80419#c92">Comment # 92</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - XCOM: Enemy Unknown Causes lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=80419">bug 80419</a> from <a class="email" href="mailto:jfonseca@vmware.com" title="Jose Fonseca <jfonseca@vmware.com>"> Jose Fonseca</a> <pre>(In reply to Daniel Exner from <a href="show_bug.cgi?id=80419#c91">comment #91</a>) > So it seems like it is indeed a Bug in the game to try to address this index > element but also the operation should not crash and its unspecified > behaviour. > > Perhaps radeonsi should handle it the same as other mesa drivers to for the > sake of cosistency. Yes, crashing should be avoided. But correct rendering, no, not generally. Not unless it can be without performance impact (which is probably not the case.) Otherwise it would be sacrificing the performance of correct GL apps, for the sake of buggy GL apps. Which is rewarding the wrong behavior. It's not that hard: the start/end parameters are hints precisely aimed at enabling the driver to do performance optimizations. If the application developers can't get them right, just them don't set to invalid values! Use 0 / ~0 which is guaranteed to work. This way the application developers that actually bothered to get them right don't get penalized. Everybody's happy. Maybe it would help if Mesa's KHR_debug / apitrace checked for this sort of error.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>