From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29013] New: [r300g] translate_rgb_op: unknown opcode ILLEGAL OPCODE
Date: Mon, 12 Jul 2010 01:51:24 -0700 (PDT) [thread overview]
Message-ID: <bug-29013-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29013
Summary: [r300g] translate_rgb_op: unknown opcode ILLEGAL
OPCODE
Product: Mesa
Version: git
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: remi.meier@gmail.com
Created an attachment (id=36952)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36952)
RADEON_DEBUG="fp" output
A small fragment shader produces the following output:
--------------------------------------------------------------
r300: Unknown TGSI/RC opcode: CAL
r300: Unknown TGSI/RC opcode: BGNSUB
r300: Unknown TGSI/RC opcode: ENDSUB
r300 FP: Compiler Error:
r500_fragprog_emit.c::translate_rgb_op(): translate_rgb_op: 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.
--------------------------------------------------------------
The shader looks like this:
--------------------------------------------------------------
vec3 floatToColor(float x)
{
if(x == 1.0)
return vec3(0, 0, 0);
}
void main()
{
gl_FragColor.rgb = floatToColor(1);
}
--------------------------------------------------------------
RADEON_DEBUG="fp" output is attached
--
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-07-12 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 8:51 bugzilla-daemon [this message]
2010-08-18 2:19 ` [Bug 29013] [r300g] translate_rgb_op: unknown opcode ILLEGAL OPCODE 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-29013-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.