From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43871] New: shader with uniform array/record and if clauses is not translated correctly into TGSI IR
Date: Thu, 15 Dec 2011 22:48:05 +0000 [thread overview]
Message-ID: <bug-43871-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=43871
Bug #: 43871
Summary: shader with uniform array/record and if clauses is not
translated correctly into TGSI IR
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: vljn@ovi.com
Hi,
the following fragment shader :
__
#version 130
uniform int mode;
uniform vec3 red;
uniform struct {
vec3 green;
vec3 blue;
} teststruct;
uniform vec3 testarray[3];
out vec3 fragColor;
void main()
{
if (mode == 0)
fragColor = red;
if (mode == 1)
fragColor = teststruct.green + teststruct.blue;
if (mode == 2)
{
fragColor = vec3(0.);
for(int i = 0; i < 3; i++)
fragColor += testarray[i];
}
}
__
is lowered to :
__
FRAG
PROPERTY FS_COLOR0_WRITES_ALL_CBUFS 1
DCL IN[0], COLOR, LINEAR
DCL OUT[0], COLOR
0: MOV OUT[0], IN[0]
1: END
__
using mesa from git, swrast, and setting glsl supported version to 130 in
st_extensions.c ; glsl_compiler --dump-lir seems correct, so it might be an
issue with glsl-to-tgsi.
--
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:[~2011-12-15 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 22:48 bugzilla-daemon [this message]
2012-09-03 10:56 ` [Bug 43871] shader with uniform array/record and if clauses is not translated correctly into TGSI IR 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-43871-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.