From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65448] New: Driver fails to compile complex shaders
Date: Thu, 06 Jun 2013 09:29:13 +0000 [thread overview]
Message-ID: <bug-65448-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1220 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65448
Priority: medium
Bug ID: 65448
Assignee: dri-devel@lists.freedesktop.org
Summary: Driver fails to compile complex shaders
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: greg@chown.ath.cx
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
The r600 driver fails to translate TGSI to bytecode for complex shaders.
https://www.shadertoy.com/view/MdX3Rr is an example for this. The fragment
shader compiles into a pretty big TGSI program (about 6500 instructions). r600
takes a long time (tens of seconds) trying to transform it into bytecode, but
in then end it fails:
EE ../../../../../mesa/src/gallium/drivers/r600/r600_shader.c:158
r600_pipe_shader_create - translation from TGSI failed !
EE ../../../../../mesa/src/gallium/drivers/r600/r600_state_common.c:753
r600_shader_select - Failed to build shader variant (type=1) -1
This happens with many of the shaders from shadertoy.com.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2567 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-06-06 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 9:29 bugzilla-daemon [this message]
2019-09-18 19:03 ` [Bug 65448] Driver fails to compile complex shaders 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-65448-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.