From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29437] New: [r300g] glean/glsl1-function fails with unknown opcode errors
Date: Sat, 7 Aug 2010 09:31:57 -0700 (PDT) [thread overview]
Message-ID: <bug-29437-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29437
Summary: [r300g] glean/glsl1-function fails with unknown opcode
errors
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: plaes@plaes.org
Kernel: 2.6.35
Mesa: git master d64a119c28376d7ce069dcec044ff9af7f93ff9c
Results for glean/glsl1-function with early return (1)
Returncode: 0
Errors:
r300: Unknown TGSI/RC opcode: CAL
r300: Unknown TGSI/RC opcode: BGNSUB
r300: Unknown TGSI/RC opcode: ENDSUB
r300 FP: Compiler Error:
r300_fragprog_emit.c::translate_rgb_opcode(): translate_rgb_opcode: Unknown
opcode ILLEGAL OPCODE
Using a dummy shader instead.
If there's an 'unknown opcode' message, please file a bug report and attach
this log.
Output:
----------------------------------------------------------------------
GLSL test 1: test basic Shading Language functionality.
glsl1: Running single test: function with early return (1)
FAILURE:
Shader test: function with early return (1)
Expected color: 0.25, 0.25, 0.25, 0.25
Observed color: 0, 0, 0, 1
glsl1: FAIL rgba8, db, z24, s8, win+pmap, id 33
0 tests passed, 1 tests failed.
--
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-08-07 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 16:31 bugzilla-daemon [this message]
2010-08-07 16:32 ` [Bug 29437] [r300g] glean/glsl1-function fails with unknown opcode errors bugzilla-daemon
2010-08-18 2:14 ` 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-29437-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