From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 90347] New: [NVE0+] Failure to insert texbar under some circumstances (causing bad colors in Terasology)
Date: Wed, 06 May 2015 18:38:07 +0000 [thread overview]
Message-ID: <bug-90347-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2241 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90347
Bug ID: 90347
Summary: [NVE0+] Failure to insert texbar under some
circumstances (causing bad colors in Terasology)
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Created attachment 115602
--> https://bugs.freedesktop.org/attachment.cgi?id=115602&action=edit
terasology.tgsi
The problem is that the attached shader compiles to:
...
34: mov u32 $r0 $r3 (8)
35: mov u32 $r1 $r5 (8)
36: tex 2D $r0 $s0 f32 $r0t $r0d (8)
37: join mov u32 $r7 $r1 (8)
BB:3 (4 instructions) - idom = BB:0, df = { BB:4 }
-> BB:4 (forward)
38: mov u32 $r0 $r3 (8)
39: mov u32 $r1 $r5 (8)
40: tex 2D $r1 $s0 f32 $r0t $r0d (8)
41: join mov u32 $r7 $r1 (8)
...
And there is no texbar before the mov happens. This causes funky rendering in
Terasology.
Somehow things get merged during RA s.t. the findFirstUses logic decides that
the tex itself is a use (it isn't!) and so it never picks up on the actual use
in that BB (since there's a check to make sure that we only pick the earliest
use in a BB). This much shorter shader reproduces a similar issue as well:
FRAG
DCL IN[0], COLOR, COLOR
DCL OUT[0], COLOR
DCL OUT[1], COLOR[1]
DCL SAMP[0]
DCL SAMP[1]
DCL TEMP[0..4], LOCAL
IMM[0] FLT32 { 0.0010, 1.0000, 0.0000, 2.5000}
5: MOV TEMP[0].xy, IN[0].xyxx
7: FSLT TEMP[2].x, IMM[0].yyyy, IN[0].xxxx
10: UIF TEMP[2].xxxx :0
30: TEX TEMP[1], TEMP[0], SAMP[0], 2D
32: ELSE :0
34: TEX TEMP[1], TEMP[0], SAMP[1], 2D
36: ENDIF
47: UIF TEMP[2].xxxx :0
50: MUL TEMP[1], TEMP[1], IMM[0].xyyy
54: ENDIF
84: MOV TEMP[0].xyz, TEMP[1].xyzx
93: MOV TEMP[1].xyz, TEMP[0].wwww
94: MOV OUT[0], TEMP[0]
95: MOV OUT[1], TEMP[1]
97: END
--
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: 3627 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-05-06 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 18:38 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-90347-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-06-15 18:46 ` [Bug 90347] [NVE0+] Failure to insert texbar under some circumstances (causing bad colors in Terasology) 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-90347-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.