[Bug 96320] [glsl] C-style const arrays trigger assertion in GLSL 4.30

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96320

Matt Turner <mattst88 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |idr at freedesktop.org
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #4 from Matt Turner <mattst88 at gmail.com> ---
Interesting. Thanks for the heads up.

Looks like the difference in behavior between 4.20 and 4.30 is due to commit
92635a84a.

Ian, it looks like adding 'const' to a declaration and initializer like

>     float[] EXAMPLE1 = {1.0, 2.0, 3.0};

under #version 430 is enough to trigger the problem.

It seems strange to consider "1.0, 2.0, 3.0" to be a constant expression in the
same vein as the example with "float a[2,3]".

So I think we're doing something wrong and returning false is papering over the
problem.

I don't think comma separated lists of an aggregate initializer are intended
treated as constant expressions.

I'm going to reopen for now.

-- 
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/20160606/59cca3fa/attachment.html>