<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Access violation on glDrawArrays with count >= 2048" href="https://bugs.freedesktop.org/show_bug.cgi?id=107295#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Access violation on glDrawArrays with count >= 2048" href="https://bugs.freedesktop.org/show_bug.cgi?id=107295">bug 107295</a> from <a class="email" href="mailto:sroland@vmware.com" title="Roland Scheidegger <sroland@vmware.com>"> Roland Scheidegger</a> <pre>(In reply to Paul from <a href="show_bug.cgi?id=107295#c7">comment #7</a>) > It's good to know you managed to pinpoint the issue, even if it's tricky to > solve. Is there a particular reason to choose emit over pipeline? Does it > perform better, for example? Yes, pipeline is more costly. emit is a passthrough path which is quite a bit easier (pipeline will decompose tri strips etc. emitting tris, whereas emit will leave things alone). > I'm also wondering if this issue is fully llvmpipe specific, or does it also > affect softpipe, swr or any other of the hardware based drivers? swr doesn't use draw, so is unaffected. Most hw drivers don't use draw neither, some do (i915), some might (some cut-down r300 based chips) but they don't expose (I believe) geometry shaders. softpipe is - it doesn't use llvm-based draw by default (but you can enable that too), but the non-llvm paths are basically the same there (just set GALLIUM_DRIVER=softpipe and it'll crash all the same). > What about VMware Fusion (I get the idea it's also based on mesa)? The gl guest driver is, and it might use draw but only for fallbacks (I am not sure you'd be able to hit this case, probably not). The code running on the host side, no, at least not hw based rendering.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>