From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 99532] Compute shader doesn't give right result under some circumstances Date: Wed, 25 Jan 2017 13:44:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0897620522==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0897620522== Content-Type: multipart/alternative; boundary="14853518750.Ed47E3F.15616"; charset="UTF-8" --14853518750.Ed47E3F.15616 Date: Wed, 25 Jan 2017 13:44:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D99532 --- Comment #7 from Boyan Ding --- (In reply to Ilia Mirkin from comment #6) > Oh wait - while there are 2 compute shaders, you only use one of them (the > one with all the shared atomics). Also need to double-check that it's not= an > earlier draw messing things up (e.g. that the compute shader is getting t= he > proper inputs). But my bet is on an issue in the compute shader. I agree with you, since the same compute shader input was also used in subsequent rendering. If that were wrong, the following render would also be incorrect. --=20 You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.= --14853518750.Ed47E3F.15616 Date: Wed, 25 Jan 2017 13:44:35 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 7 on bug 99532<= /a> from Boyan Ding 
(In reply to Ilia Mirkin from comment #6)
> Oh wait - while there are 2 compute shaders, you=
 only use one of them (the
> one with all the shared atomics). Also need to double-check that it's =
not an
> earlier draw messing things up (e.g. that the compute shader is gettin=
g the
> proper inputs). But my bet is on an issue in the compute shader.

I agree with you, since the same compute shader input was also used in
subsequent rendering. If that were wrong, the following render would also be
incorrect.

You are receiving this mail because:
  • You are the QA Contact for the bug.
  • You are the assignee for the bug.
= --14853518750.Ed47E3F.15616-- --===============0897620522== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============0897620522==--