From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71777] New: R600 stuck while compiling shader for Unigine Heaven 3.0
Date: Tue, 19 Nov 2013 09:40:30 +0000 [thread overview]
Message-ID: <bug-71777-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1063 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71777
Priority: medium
Bug ID: 71777
Assignee: dri-devel@lists.freedesktop.org
Summary: R600 stuck while compiling shader for Unigine Heaven
3.0
Severity: normal
Classification: Unclassified
OS: All
Reporter: marvin24@gmx.de
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 89455
--> https://bugs.freedesktop.org/attachment.cgi?id=89455&action=edit
diff of the relevant shader dump with and without the patch
commit 88c8f19 (r600/llvm: Store inputs in function arguments) causes some
infinite loop compiling a shader in UH 3.0. Works fine with R600_LLVM=0 or by
reverting the patch. I attached a shader dump diff with and without the patch.
See also
http://lists.freedesktop.org/archives/mesa-dev/2013-November/048433.html.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2651 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:[~2013-11-19 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 9:40 bugzilla-daemon [this message]
2013-11-22 0:50 ` [Bug 71777] R600 stuck while compiling shader for Unigine Heaven 3.0 bugzilla-daemon
2013-11-25 12:08 ` bugzilla-daemon
2013-12-13 19:15 ` bugzilla-daemon
2013-12-14 22:58 ` 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-71777-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 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.