Bug 60047

Summary: [softpipe] piglit masked-clear regression
Product: Mesa Reporter: Vinson Lee <vlee>
Component: Mesa coreAssignee: mesa-dev
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium CC: maraeo
Version: gitKeywords: regression
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Vinson Lee 2013-01-30 00:46:59 UTC
mesa: 02b6da1e87ddf333a71b37234c356b3f3f7f58be (master)

$ ./bin/masked-clear -auto
Mesa warning: failed to remap glClampColorARB
Mesa warning: failed to remap glTexBufferARB
Mesa warning: failed to remap glFramebufferTextureARB
Mesa warning: failed to remap glVertexAttribDivisorARB
Mesa warning: failed to remap glProgramParameteriARB
masked-clear: stencil buffer value is 3, expected 2
        GL_STENCIL_WRITEMASK = 0x2
masked-clear: stencil buffer value is 7, expected 4
        GL_STENCIL_WRITEMASK = 0x4
masked-clear: stencil buffer value is 15, expected 8
        GL_STENCIL_WRITEMASK = 0x8
masked-clear: stencil buffer value is 31, expected 16
        GL_STENCIL_WRITEMASK = 0x10
masked-clear: stencil buffer value is 63, expected 32
        GL_STENCIL_WRITEMASK = 0x20
masked-clear: stencil buffer value is 127, expected 64
        GL_STENCIL_WRITEMASK = 0x40
masked-clear: stencil buffer value is 255, expected 128
        GL_STENCIL_WRITEMASK = 0x80
PIGLIT: {'result': 'fail' }


cabe4fbb852f3c335937e3576db85d0143cb6c12 is the first bad commit
commit cabe4fbb852f3c335937e3576db85d0143cb6c12
Author: Marek Olšák <maraeo@gmail.com>
Date:   Mon Jan 14 06:57:28 2013 +0100

    st/mesa: always assume separate depth and stencil clear is supported

    All drivers implement it now.

    Reviewed-by: Brian Paul <brianp@vmware.com>

:040000 040000 dcfc8a78bba351a39a856c95d9ad3cf64021f552 6cd989d9615cbe17dda7c0b46891dcb309579df2 M      src
bisect run success
Comment 1 Brian Paul 2013-02-12 15:15:16 UTC
Fixed by commit 4bfdef87e66bfb2459af570351798d7754ddfb9f

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.