From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28624] New: fails to compile some fragment programs of Enemy Territory: Quake Wars
Date: Sun, 20 Jun 2010 06:44:50 -0700 (PDT) [thread overview]
Message-ID: <bug-28624-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28624
Summary: fails to compile some fragment programs of Enemy
Territory: Quake Wars
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: aaalmosss@gmail.com
Created an attachment (id=36379)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36379)
stderr with RADEON_DEBUG=fp
The driver prints the following:
r300compiler error: r300_fragprog_emit.c::begin_tex(): Too many texture
indirections
r300 FP: Compiler Error:
r300_fragprog_emit.c::begin_tex(): Too many texture indirections
Using a dummy shader instead.
The attached log is done with RADEON_DEBUG=fp. It is stderr only, because et:qw
fails to start (stops at 'loading UI') if stdout is redirected as well.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-06-20 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 13:44 bugzilla-daemon [this message]
2010-06-20 14:20 ` [Bug 28624] [r300g] too many texture indirections (was: fails to compile some fragment programs of Enemy Territory: Quake Wars) bugzilla-daemon
2010-06-20 17:31 ` bugzilla-daemon
2010-07-05 16:26 ` bugzilla-daemon
2010-07-09 5:05 ` bugzilla-daemon
2010-07-09 18:53 ` bugzilla-daemon
2010-07-09 19:00 ` 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-28624-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