From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85696] New: [regression] r600g+nine: Bioshock shader failure after recent changes
Date: Fri, 31 Oct 2014 12:08:42 +0000 [thread overview]
Message-ID: <bug-85696-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1762 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85696
Bug ID: 85696
Summary: [regression] r600g+nine: Bioshock shader failure after
recent changes
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: david@ixit.cz
HW: HD6550D
I tested Bioshock against mesa-git (+nine) about 10 days ago (I'd say maybe 6
days, but 10 for sure). It worked.
Now after gallium-nine rebase I get this error. I did research, tested old
kernel (3.16.2, now I'm with 3.16.6), tried older wine (1.7.28, now I'm at
1.7.29), but no change. Nine shader code should be also untouched.
I got report, that Bioshock on radeonsi (HD7950 I think) works with Nine
correctly.
Does anyone has idea, what can cause this issue?
error at : VFETCH __, __, __, t153||FP@R5.w, R20.x||@R5.y, __, __, __
: operand value R20.x||@R5.y was not previously written to its gpr
error at : VFETCH t150||FP@R6.x, t151||FP@R6.y, t152||FP@R6.z, __,
R20.x||@R5.y, __, __, __
: operand value R20.x||@R5.y was not previously written to its gpr
error at : VFETCH __, __, __, t144||FP@R2.z, R20.x||@R5.y, __, __, __
: operand value R20.x||@R5.y was not previously written to its gpr
error at : VFETCH __, __, __, t117||FP@R0.w, R20.x||@R5.y, __, __, __
: operand value R20.x||@R5.y was not previously written to its gpr
sb/sb_ra_checker.cpp:46:run: Assertion `sh.errors.empty()' failed.
Thank you
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3245 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 reply other threads:[~2014-10-31 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 12:08 bugzilla-daemon [this message]
2014-10-31 12:19 ` [Bug 85696] [regression] r600g+nine: Bioshock shader failure after recent changes 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 ` [Bug 85696] " bugzilla-daemon
2014-11-20 1:29 ` 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@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