[Bug 89508] Bad int(floatBitsToInt(vec4))

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=89508

--- Comment #6 from Iago Toral <itoral at igalia.com> ---
I found something interesting: the test expects addr0 to get values 0, 1, 2, 3,
then exit the loop in the 5th iteration, so I edited the code in the loop to
add this conditional for the assignment of temp[9]:

addr0 = int(floatBitsToInt(temps[10].xxxx));
if (addr0 >= 4)
   temps[9] = vec4(1.0, 0, 0, 0);
else
   temps[9] += temps[addr0];

Basically, I wanted to confirm that addr0 was being assigned a value that was
not expected (by forcing a red color as the output), but surprisingly, adding
this conditional makes the test pass!

Based on this, I think the problem here must be related with an optimization
pass that, for some reason, changes its behavior when the conditional is
present.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20150312/2a8a9682/attachment.html>