Summary: | piglit ext_texture_integer-api-teximage regression | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | brianp |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Vinson Lee
2012-02-14 22:43:12 UTC
I think this is actually a bug in the piglit test. The glTexSubImage call in question can generate either GL_INVALID_ENUM or GL_INVALID_OPERATION depending on what order glTexSubImage() does its parameter error checking: From the spec: INVALID_ENUM is generated by DrawPixels, TexImage* and SubTexImage* if <format> is one of the integer component formats described in table 3.6 and <type> is FLOAT. and: INVALID_OPERATION is generated by TexImage* and SubTexImage* if the texture internalformat is an integer format as described in table 3.16 and <format> is not one of the integer component formats described in table 3.6, or if the internalformat is not an integer format and <format> is an integer format. I can fix the piglit test, but after reviewing Mesa it looks like we're missing the later error check for glTexSubImage. I'll work on that too... Fixed w/ piglit 19f34bf1338cfc4a93d777564aedb0bf805140d5 and Mesa commit 6f3d91840945fbd9221a247e4f95b32c4051f202 |
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.