<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#c95">Comment # 95</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 Roland Scheidegger from <a href="show_bug.cgi?id=80419#c94">comment #94</a>) > Created <a href="attachment.cgi?id=120734" name="attach_120734" title="apitrace patch for honoring range in DrawRangeElementsX commands">attachment 120734</a> <a href="attachment.cgi?id=120734&action=edit" title="apitrace patch for honoring range in DrawRangeElementsX commands">[details]</a> <a href='page.cgi?id=splinter.html&bug=80419&attachment=120734'>[review]</a> [review] > apitrace patch for honoring range in DrawRangeElementsX commands > > So you'd want something like this (totally untested) patch for apitrace? > Makes sense I guess that the specified range not only means the supplied > indices have to be inside that range, but it also works the other way round > (driver can rely on the specified range being accessible) - otherwise the > driver would still need to scan the actual index buffer. (Albeit since for > this app the ranges seem to be pretty bogus who knows if the memory inside > the specified range but not used in the actual indices is really always > accessible.) Yes, this does indeed make sense. For VBOs, the start/end range is a hint (the OpenGL shouldn't crash if the start/end range goes beyond the VBO size), but for user memory arrays, there's no reliable way to know where user memory is supposed to stop -- the start/end range is it. > I am actually wondering if it would be legal if the memory isn't accessible > below the start value (apitrace surely couldn't handle that)... I don't think it's worth worrying about that.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>