[Bug 103214] GLES CTS functional.state_query.indexed.atomic_counter regression

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 103214
           Summary: GLES CTS functional.state_query.indexed.atomic_counter
                    regression
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: airlied at freedesktop.org
          Reporter: mark.a.janes at intel.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Beginning with the series ending in:
9926af0e7195c245d6b9d11b0fee6ba146987dbf
Author:     Dave Airlie <airlied at redhat.com>
mesa/st: fix atomic buffer sizing to align with ssbo.

This respects the size from the range setting like ssbo.

Reviewed-by: Samuel Pitoiset <samuel.pitoiset at gmail.com>
Reviewed-by: Iago Toral Quiroga <itoral at igalia.com>

The following tests regressed on IVB+:
ES31-CTS.core.shader_atomic_counters.basic-buffer-bind
ES31-CTS.functional.state_query.indexed.atomic_counter_buffer_size_getbooleani_v
ES31-CTS.functional.state_query.indexed.atomic_counter_buffer_size_getinteger64i_v
ES31-CTS.functional.state_query.indexed.atomic_counter_buffer_size_getintegeri_v
ES31-CTS.functional.state_query.indexed.atomic_counter_buffer_start_getbooleani_v
ES31-CTS.functional.state_query.indexed.atomic_counter_buffer_start_getinteger64i_v
ES31-CTS.functional.state_query.indexed.atomic_counter_buffer_start_getintegeri_v

Also, ES32 variants regressed with the same errors.

Sample output:
-----------------------------------------------------------------------
ES31-CTS.core.shader_atomic_counters.basic-buffer-bind

Atomic Counter Buffer - binding
Verify that binding buffer objects to ATOMIC_COUNTER_BUFFER (indexed) target
works as expected. In particualr make sure that binding with BindBufferBase and
BindBufferRange
also bind to generic binding point and deleting buffer that is currently bound
unbinds it. Tested
commands: BindBuffer, BindBufferBase and BindBufferRange.
glGetIntegerv(GL_MAX_ATOMIC_COUNTER_BUFFER_BINDINGS, 0x00007ffe4f950128);
// data = { 90 }
MAX_ATOMIC_COUNTER_BUFFER_BINDINGS: 90
glGetIntegerv(GL_ATOMIC_COUNTER_BUFFER_BINDING, 0x00007ffe4f9500e8);
// data = { 0 }
glGetInteger64v(GL_ATOMIC_COUNTER_BUFFER_BINDING, 0x00007ffe4f9500e0);
// data = { 0 }
glGetFloatv(GL_ATOMIC_COUNTER_BUFFER_BINDING, 0x00007ffe4f9500dc);
// data = { 0 }
glGetBooleanv(GL_ATOMIC_COUNTER_BUFFER_BINDING, 0x00007ffe4f9500db);
// data = { GL_FALSE }
glGetIntegeri_v(GL_ATOMIC_COUNTER_BUFFER_BINDING, 0, 0x00007ffe4f9500f8);
// data = { 0 }
glGetInteger64i_v(GL_ATOMIC_COUNTER_BUFFER_BINDING, 0, 0x00007ffe4f9500f0);
// data = { 0 }
glGetInteger64i_v(GL_ATOMIC_COUNTER_BUFFER_START, 0, 0x00007ffe4f9500f0);
// data = { -1 }
GL_ATOMIC_COUNTER_BUFFER_START state is incorrect (GetInteger64i_v, is: -1,
expected: 0, index: 0)
glGetInteger64i_v(GL_ATOMIC_COUNTER_BUFFER_SIZE, 0, 0x00007ffe4f9500f0);
// data = { -1 }
GL_ATOMIC_COUNTER_BUFFER_SIZE state is incorrect (GetInteger64i_v, is: -1,
expected: (0 or 0), index: 0)
Test Run() failed
glDeleteBuffers(1, { 0 });
-----------------------------------------------------------------------

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