From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99532] New: Compute shader doesn't give right result under some circumstances
Date: Wed, 25 Jan 2017 11:35:33 +0000 [thread overview]
Message-ID: <bug-99532-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2132 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99532
Bug ID: 99532
Summary: Compute shader doesn't give right result under some
circumstances
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: stu_dby-KN7UnAbNpbg@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Created attachment 129135
--> https://bugs.freedesktop.org/attachment.cgi?id=129135&action=edit
apitrace of my program
When I'm doing a course project in my compute graphics class, I found my
program didn't fully work on nouveau while it was working fine on intel and
nvidia proprietary drivers. It is a program using deferred shading with some
shadow map techniques, and it has an option to draw a "histogram" of depth
distribution sampled by a compute shader. I found histogram was showing wrong
results (totally blank) on nouveau.
After looking into the problem for a while, I happened to find that if I didn't
render the histogram (i.e. didn't use compute shader to sample) on the first
frame, the histogram would go wrong, otherwise, it would be okay.
This problem can be reproduced with the attached apitrace file, recorded with
simplified program and trimmed to contain only 4 frames. The first 2 frames are
mainly initialization and the third frame renders the scene from one angle
without generating histogram. The last frame renders the scene from another
angle and generates a histogram at bottom-right edge, which is completely blank
on nouveau. However, if the trace is further trimmed to contain frame 0,1,3,
the histogram will render correctly. (Results of the two will be attached
below)
I'm willing provide assistance if needed.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3589 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2017-01-25 11:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 11:35 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-99532-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-01-25 11:36 ` [Bug 99532] Compute shader doesn't give right result under some circumstances bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 11:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 13:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 13:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 13:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 13:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 13:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 13:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 13:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-25 14:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-26 6:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-26 6:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-06 12:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-07 12:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-07 12:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-07 12:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-12 18:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-13 1:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-14 2:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99532-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.