Summary: | [r300g] piglit vs-clip-vertex-const-reject fails | ||
---|---|---|---|
Product: | Mesa | Reporter: | Pavel Ondračka <pavel.ondracka> |
Component: | Drivers/Gallium/r300 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | low | CC: | stereotype441 |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Pavel Ondračka
2012-02-10 13:57:38 UTC
Before commit 7d68c639ddb0f9df45cf698b8e8227bf1860b5fe, Mesa's support for gl_ClipVertex was completely broken, because Mesa couldn't distinguish between gl_ClipVertex and gl_Position. The bugs in Mesa happened to line up in such a way that the Piglit test vs-clip-vertex-const-reject passed, but this was not a sign that gl_ClipVertex in any way worked; it was just a coincidence. Commit 7d68c639ddb0f9df45cf698b8e8227bf1860b5fe laid the groundwork for actual non-buggy support for gl_ClipVertex, and a later patch. However, it was impossible to lay this groundwork without causing vs-clip-vertex-const-reject to stop passing. This is not a true regression, because vs-clip-vertex-const-reject was only passing by dumb luck before this commit; it wasn't passing because of any correct functionality in Mesa. In order for gl_ClipVertex to work on any particular driver (for example r300g or llvmpipe), additional back-end work needs to be done. I have done this back-end work for i965 (see commit d912669034eb7bf5c162358a7a574ec7a4c963c7). However, I don't have the expertise to do it for other back-ends. If anyone who is knowledgeable about r300g RV530 or llvmpipe would like to do the corresponding back-end work for those drivers, I would be happy to help--feel free to email me at stereotype441@gmail.com if commit d912669034eb7bf5c162358a7a574ec7a4c963c7 doesn't provide enough information. Incidentally, the same situation also exists for i915. OK, reassigning to r300g per commment 1. Also lowering importance. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/340. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.