<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Regression] [Bisected] assert in fragment shader compilation when SIMD32 is enabled"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110507#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Regression] [Bisected] assert in fragment shader compilation when SIMD32 is enabled"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110507">bug 110507</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=110507#c8">comment #8</a>)
<span class="quote">> This will not affect users unless they are overriding the simd32
> configuration for fragment shaders. During our engineering meeting, we
> decided that this issue should not block the release.</span >
Should there be e.g. mesa-19.3 tracker where regressions that don't block
current release would get moved? (to make sure they don't fall between the
cracks later on)</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>