<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - GLES CTS functional.state_query.indexed.atomic_counter regression"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103214">103214</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GLES CTS functional.state_query.indexed.atomic_counter regression
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>critical
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/DRI/i965
</td>
</tr>
<tr>
<th>Assignee</th>
<td>airlied@freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>mark.a.janes@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Beginning with the series ending in:
9926af0e7195c245d6b9d11b0fee6ba146987dbf
Author: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>>
mesa/st: fix atomic buffer sizing to align with ssbo.
This respects the size from the range setting like ssbo.
Reviewed-by: Samuel Pitoiset <<a href="mailto:samuel.pitoiset@gmail.com">samuel.pitoiset@gmail.com</a>>
Reviewed-by: Iago Toral Quiroga <<a href="mailto:itoral@igalia.com">itoral@igalia.com</a>>
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 });
-----------------------------------------------------------------------</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>