Not only is the glean pointSprite test failing on 965, but it is also broken in the software rasterizer (swrast_dri.so). The output of the test is below. It looks like only the test that set the coordinate origin to GL_LOWER_LEFT are failing. Could this be related to recent TNL-to-shader changes? Incorrect pixel at (19, 19): it should be rendered with color: (0, 1, 0), actual read: (0, 0, 1) Primitive type: GL_POINTS Coord Origin at: GL_LOWER_LEFT PointSize: 1.85 Incorrect pixel at (19, 19): it should be rendered with color: (0, 1, 0), actual read: (0, 0, 1) Primitive type: GL_POLYGON Coord Origin at: GL_LOWER_LEFT PointSize: 1.85 pointSprite: FAIL rgba8, db, z24, s8, win+pmap, id 33 5 tests passed, 2 tests failed. Incorrect pixel at (19, 19): it should be rendered with color: (0, 1, 0), actual read: (0, 0, 1) Primitive type: GL_POINTS Coord Origin at: GL_LOWER_LEFT PointSize: 1.85 Incorrect pixel at (19, 19): it should be rendered with color: (0, 1, 0), actual read: (0, 0, 1) Primitive type: GL_POLYGON Coord Origin at: GL_LOWER_LEFT PointSize: 1.85 pointSprite: FAIL rgba8, db, z24, s8, win+pmap, id 34 5 tests passed, 2 tests failed. Incorrect pixel at (19, 19): it should be rendered with color: (0, 1, 0), actual read: (0, 0, 1) Primitive type: GL_POINTS Coord Origin at: GL_LOWER_LEFT PointSize: 1.85 Incorrect pixel at (19, 19): it should be rendered with color: (0, 1, 0), actual read: (0, 0, 1) Primitive type: GL_POLYGON Coord Origin at: GL_LOWER_LEFT PointSize: 1.85 pointSprite: FAIL rgba8, win+pmap, id 99 5 tests passed, 2 tests failed.
I'm not sure what might have changed to cause the failure, but digging into the swrast case, it looks like the texcoords need to be more carefully computed for the spans. I'm checking in a fix for that. In the progs/demos/spriteblast demo, press 'o' to toggle the sprite coord origin. The "GL" should flip. Does that work on i965?
This seems to be working for both swrast and i965 now. All my pointsprite tests pass.
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.