From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85696] r600g+nine: Bioshock shader failure after 7b1c0cbc90d456384b0950ad21faa3c61a6b43ff
Date: Thu, 20 Nov 2014 01:17:54 +0000 [thread overview]
Message-ID: <bug-85696-502-suClR8yaTF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-85696-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1399 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85696
David Heidelberg (okias) <david@ixit.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|bisected, regression |
Summary|[regression] r600g+nine: |r600g+nine: Bioshock shader
|Bioshock shader failure |failure after
|after |7b1c0cbc90d456384b0950ad21f
|7b1c0cbc90d456384b0950ad21f |aa3c61a6b43ff
|aa3c61a6b43ff |
--- Comment #4 from David Heidelberg (okias) <david@ixit.cz> ---
It's bug in Nine.
Instead of one available ADDR[0], we try use DCL ADDR[0..1].
ADDR[0] is allocated by LOOP (for counter purposes) and then later is allocated
ADDR[1].
0 is the address register (already allocated by LOOP, but in this case unused)
1 is UBO index register (misused by location for MOVA (coverted)-> ARR)
2 is sampler index register (not used, correctly).
Axel had idea we could do something like:
. if wants to use rL to index constant register
. . if a0 is used somewhere in the shader
. . then copy the content to temp. load rL to a0. do the op. restore a0
. . else copy rL to a0 and use it
. else do nothing particular
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2830 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-20 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 12:08 [Bug 85696] New: [regression] r600g+nine: Bioshock shader failure after recent changes bugzilla-daemon
2014-10-31 12:19 ` [Bug 85696] " bugzilla-daemon
2014-10-31 12:53 ` bugzilla-daemon
2014-10-31 13:29 ` bugzilla-daemon
2014-10-31 16:51 ` [Bug 85696] [regression] r600g+nine: Bioshock shader failure after 7b1c0cbc90d456384b0950ad21faa3c61a6b43ff bugzilla-daemon
2014-11-01 23:43 ` bugzilla-daemon
2014-11-20 1:17 ` bugzilla-daemon [this message]
2014-11-20 1:29 ` [Bug 85696] " bugzilla-daemon
2014-12-08 23:09 ` bugzilla-daemon
2015-02-06 1:48 ` bugzilla-daemon
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-85696-502-suClR8yaTF@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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