Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 78161] New: [NV96] Artifacts in output of fragment program containing not unrolled loops with conditional break
Date: Thu, 01 May 2014 15:29:05 +0000	[thread overview]
Message-ID: <bug-78161-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]

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

          Priority: medium
            Bug ID: 78161
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: [NV96] Artifacts in output of fragment program
                    containing not unrolled loops with conditional break
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: gzregozrw-5tc4TXWwyLM@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/DRI/nouveau
           Product: Mesa

Created attachment 98301
  --> https://bugs.freedesktop.org/attachment.cgi?id=98301&action=edit
apitrace of simple test program.

Problem appear in shaders containing loops with conditional break when loop is
not unrolled by nouveau. I checked emitted code with ST_DEBUG=tgsi
NV50_PROG_DEBUG=1.
Tested with Mesa 10.2.0-devel (git-475f5ff) from 2014-04-30.
This bug exists for more than year, I first saw it in 2013-02.
I think that artifacts appear in areas where is big difference in number of
iterations executed for pixel before breaking from loop.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2690 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2014-05-01 15:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01 15:29 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-78161-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-05-01 15:29   ` [Bug 78161] [NV96] Artifacts in output of fragment program containing not unrolled loops with conditional break bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-01 15:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-01 15:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-01 15:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-02  1:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-02  1:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-02  2:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-02  2:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-02  7:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-20 14:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-20 14:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-28  2:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:39   ` 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-78161-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox