[Mesa-dev] [Bug 107295] Access violation on glDrawArrays with count >= 2048

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jul 20 20:37:33 UTC 2018


--- Comment #8 from Roland Scheidegger <sroland at vmware.com> ---
(In reply to Paul from comment #7)
> 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.

You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180720/5c1d362b/attachment.html>

More information about the mesa-dev mailing list