<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 - [i965] SIMD16 dual_source_blend assertion `src[i].file != GRF || src[i].width == dst.width' failed"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90629">90629</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[i965] SIMD16 dual_source_blend assertion `src[i].file != GRF || src[i].width == dst.width' failed
</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>wickmarkus@web.de
</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=116025" name="attach_116025" title="apitrace dump to reproduce this issue">attachment 116025</a> <a href="attachment.cgi?id=116025&action=edit" title="apitrace dump to reproduce this issue">[details]</a></span>
apitrace dump to reproduce this issue
Hi,
I get an assert on my IVB with mesa-master since this commit:
i965/fs: Implement integer multiply without mul/mach.
The assert is:
brw_fs.cpp:346: fs_inst* fs_visitor::LOAD_PAYLOAD(const fs_reg&, fs_reg*, int,
int): Assertion `src[i].file != GRF || src[i].width == dst.width' failed.
mattst88> I'm thinking that enabling SIMD16 in this shader allows us to see a
bug in a different area of the code we couldn't hit before :)
mattst88> it's related to dual-source blending, which I guess isn't a very
common feature
To reproduce this issue, I've attached an apitrace dump here at this report.
gdb bt:
#0 0x00007ffff6865528 in raise () from /usr/lib/libc.so.6
#1 0x00007ffff686693a in abort () from /usr/lib/libc.so.6
#2 0x00007ffff685e3a7 in __assert_fail_base () from /usr/lib/libc.so.6
#3 0x00007ffff685e452 in __assert_fail () from /usr/lib/libc.so.6
#4 0x00007ffff314d603 in fs_visitor::LOAD_PAYLOAD
(this=this@entry=0x7fffffffd020, dst=..., src=src@entry=0x1af8c10,
sources=sources@entry=11,
header_size=header_size@entry=2) at brw_fs.cpp:346
#5 0x00007ffff319b732 in fs_visitor::emit_single_fb_write
(this=this@entry=0x7fffffffd020, color0=..., color1=..., src0_alpha=...,
components=components@entry=4,
exec_size=exec_size@entry=8, use_2nd_half=use_2nd_half@entry=false) at
brw_fs_visitor.cpp:3730
#6 0x00007ffff319c14a in fs_visitor::emit_fb_writes
(this=this@entry=0x7fffffffd020) at brw_fs_visitor.cpp:3772
#7 0x00007ffff315ba98 in fs_visitor::run_fs (this=this@entry=0x7fffffffd020)
at brw_fs.cpp:4344
#8 0x00007ffff315c34c in brw_wm_fs_emit (brw=brw@entry=0x7ffff7fd2040,
mem_ctx=mem_ctx@entry=0x1ad15d0, key=key@entry=0x7fffffffe1d0,
prog_data=prog_data@entry=0x7fffffffe040, fp=fp@entry=0x1aaaf90,
prog=prog@entry=0x1abde90, final_assembly_size=0x7fffffffe03c) at
brw_fs.cpp:4473
#9 0x00007ffff31de4bf in brw_codegen_wm_prog (brw=0x7ffff7fd2040,
prog=0x1abde90, fp=0x1aaaf90, key=0x7fffffffe1d0) at brw_wm.c:213
#10 0x00007ffff315ab8f in brw_fs_precompile (ctx=0x7ffff7fd2040,
shader_prog=0x1abde90, prog=0x1aaaf90) at brw_fs.cpp:4579
#11 0x00007ffff31b6210 in brw_shader_precompile (sh_prog=0x1abde90,
ctx=0x7ffff7fd2040) at brw_shader.cpp:78
#12 brw_link_shader (ctx=0x7ffff7fd2040, shProg=0x1abde90) at
brw_shader.cpp:320
#13 0x00007ffff2ff6552 in _mesa_glsl_link_shader (ctx=0x7ffff7fd2040,
prog=0x1abde90) at program/ir_to_mesa.cpp:2964
#14 0x00007ffff2f0217a in link_program (ctx=0x7ffff7fd2040, program=<optimized
out>) at main/shaderapi.c:946</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>