From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 78870] New: [r600g] Driver fails to compile shader from the game tesseract - if/endif unbalanced in shader
Date: Mon, 19 May 2014 01:44:11 +0000 [thread overview]
Message-ID: <bug-78870-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1226 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=78870
Priority: medium
Bug ID: 78870
Assignee: dri-devel@lists.freedesktop.org
Summary: [r600g] Driver fails to compile shader from the game
tesseract - if/endif unbalanced in shader
Severity: normal
Classification: Unclassified
OS: All
Reporter: tdroste@gmx.de
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 99288
--> https://bugs.freedesktop.org/attachment.cgi?id=99288&action=edit
TGSI shader dump
While trying different settings in tesseract r600g gives me this for the
maximum setting of MLAA:
EE r600_shader.c:6180 tgsi_endif - if/endif unbalanced in shader
EE r600_shader.c:157 r600_pipe_shader_create - translation from TGSI failed !
EE r600_state_common.c:750 r600_shader_select - Failed to build shader variant
(type=1) -1
The offending TGSI shader is attachend. From a simple count of UIF end ENDIF it
seems that they are not unbalanced and the problem is somewhere else.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2679 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-05-19 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 1:44 bugzilla-daemon [this message]
2019-09-18 19:16 ` [Bug 78870] [r600g] Driver fails to compile shader from the game tesseract - if/endif unbalanced in shader 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-78870-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.