<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Bizarre vertex shader results (warped geometry) unless a never executed if-branch is added."
href="https://bugs.freedesktop.org/show_bug.cgi?id=84004">84004</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>idr@freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Bizarre vertex shader results (warped geometry) unless a never executed if-branch is added.
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>delta_luca@hotmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Component</th>
<td>glsl-compiler
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=106438" name="attach_106438" title="GLSL code for the 3 vertex shaders, work-around highlighted in each case.">attachment 106438</a> <a href="attachment.cgi?id=106438&action=edit" title="GLSL code for the 3 vertex shaders, work-around highlighted in each case.">[details]</a></span>
GLSL code for the 3 vertex shaders, work-around highlighted in each case.
WebGL, chrome + firefox on various devices (all 64bit linux + intel graphics)
Devices:
1)
Ubuntu 14.04
Intel Core i5 2500K
Mesa git a3306f02 2014-09-08 from Xorg-edgers ppa
Chrome 37 + Firefox 32
2)
Chrome book pixel
Intel Core i5 3427U
Mesa 10.3.0-devel git 1751a9b
Chrome 37
3)
Fedora 20
Intel Core i7 3612QM
Mesa 10.1.5
Chrome 37
Behaviour:
Geometry rendered with 3 particular vertex shaders ends up coming out with
seemingly completely randomn positions, with triangles stretched all over the
screen in a crazy mess.
Adding a single if branch (whose condition is always false) to the shaders
fixes behaviour.
Behaviour does not occur on windows with intel drivers, or on windows/mac/linux
with nvidia drivers. Status with ATI drivers is unknown.
Our shaders are written in CG compiled to GLSL, so apologies upfront for
atrocious GLSL code. The relevant areas are highlighted. Producing a single
reproducible can be done if required, though it would take some time, please
let me know if the GLSL code is insufficient.
Screenshot without workaround:
<a href="https://drive.google.com/file/d/0B0DebLXzXCcQYVJEQ0RQSjR6QlU">https://drive.google.com/file/d/0B0DebLXzXCcQYVJEQ0RQSjR6QlU</a>
Screenshot with workaround:
<a href="https://drive.google.com/file/d/0B0DebLXzXCcQalF5WVZiWjBlY2s">https://drive.google.com/file/d/0B0DebLXzXCcQalF5WVZiWjBlY2s</a></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>