[Nouveau] [Bug 99532] Compute shader doesn't give right result under some circumstances

[bugzilla-daemon at freedesktop.org]

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

--- Comment #13 from Boyan Ding <stu_dby at 126.com> ---
Now I doubt if the problem really lies in the atomic operations, even in
compiler at all. I changed the compute shader a little bit, only letting thread
(0, 0) to accumulate its result to the ssbo (the dividing factor in histogram
fragment shader changed from 20000 to 20). This bypasses atomic operation and
shared memory, but the same problem persists.

I suspect that the input state of compute shader is somehow invalid, and that
explains why removing one frame of the trace will magically eliminate the
problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20170206/530d7eb4/attachment.html>