<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 - Blits from GL_TEXTURE_2D_MULTISAMPLE GL_INT or GL_UINT surfaces are not handled correctly"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94142">94142</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Blits from GL_TEXTURE_2D_MULTISAMPLE GL_INT or GL_UINT surfaces are not handled correctly
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</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>idr@freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>idr@freedesktop.org
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=121740" name="attach_121740" title="Assertion that also shows the problem.">attachment 121740</a> <a href="attachment.cgi?id=121740&action=edit" title="Assertion that also shows the problem.">[details]</a></span>
Assertion that also shows the problem.
For reference, use 'git blame src/mesa/drivers/common/meta_blit.c 9e30d66b'.
Assume the blit is an MSAA-MSAA blit from a GL_TEXTURE_2D_MULTISAMPLE surface
with base type GL_INT.
Line 294 sets dst_is_msaa true.
Line 313 sets shader_index to BLIT_MSAA_SHADER_2D_MULTISAMPLE_COPY.
Line 339 increments shader_index by 5, and it is now
BLIT_1X_MSAA_SHADER_2D_MULTISAMPLE_ARRAY_RESOLVE.
Similar problems exist for GL_TEXTURE_2D_MULTISAMPLE_ARRAY blits. You really
only notice this problem is a blit of one kind is followed by a blit of a kind
that conflicts.
We should have piglit tests for this.
I noticed this because, while I was making other changes, I added an assertion
like the one in the attachment. Surely dst_is_msaa must be false when doing a
resolve blit. Alas.</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>