[Bug 94188] define (or undef) defined behaves stupidly
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Feb 17 02:24:23 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=94188
Bug ID: 94188
Summary: define (or undef) defined behaves stupidly
Product: Mesa
Version: git
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority: medium
Component: glsl-compiler
Assignee: idr at freedesktop.org
Reporter: idr at freedesktop.org
QA Contact: intel-3d-bugs at lists.freedesktop.org
A shader like
#define defined gl_Position
void main()
{
defined = vec4(1.0);
}
should either file to compile at line 1 or it should "just work." Instead,
Mesa produces a fairly obtuse error message:
0:5(2): error: `defined' undeclared
0:5(2): error: value of type vec4 cannot be assigned to variable of type
error
Apparently some dEQP test expects '#define defined' and '#undef defined' to
just work, but glslang generates an error. See also
https://github.com/KhronosGroup/glslang/issues/59. Either way, Mesa's behavior
is wrong.
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160217/dfa6c431/attachment.html>
More information about the intel-3d-bugs
mailing list