[Bug 91017] [bisected, byt, bsw] arb_framebuffer_no_attachments.arb_framebuffer_no_attachments-atomic

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91017

--- Comment #1 from Kevin Rogovin <kevin.rogovin at intel.com> ---
This is NOT a framebuffer_no_attachment bug. 

Changing the test to NOT bind a framebuffer, essentially commenting out from
tests/spec/arb_framebuffer_no_attachments/atomic.c the block that binds an
attachmentless FBO: 


    glBindFramebuffer(GL_FRAMEBUFFER, fbo);

    /* Setup default width and height. */
    glFramebufferParameteri(GL_FRAMEBUFFER,
        GL_FRAMEBUFFER_DEFAULT_WIDTH, piglit_width);
    glFramebufferParameteri(GL_FRAMEBUFFER,
        GL_FRAMEBUFFER_DEFAULT_HEIGHT, piglit_height);

    /* Check that fbo is marked complete. */
    if (glCheckFramebufferStatus(GL_FRAMEBUFFER) !=
        GL_FRAMEBUFFER_COMPLETE)
        piglit_report_result(PIGLIT_FAIL);

    prog = piglit_build_simple_program(vs_source, fs_source);

    /* Check that there are no errors. */
    if (!prog || !piglit_check_gl_error(GL_NO_ERROR))
        piglit_report_result(PIGLIT_FAIL);

produces the exact same error, i.e. this error is independent of FBO no
attachments and for that matter FBO's.

The bug source is likely to be a cache flush issue that manifests on atoms()
only. Changing the reset_count() implementation to instead use glBufferData
(creating a new BO) makes the test pass.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20150618/df40e468/attachment.html>