Bug 76392

Summary: [IVB/HSW] ogl-samples: gl-320-glsl-cast-fail failure
Product: Mesa Reporter: meng <mengmeng.meng>
Component: Drivers/DRI/i965Assignee: Ian Romanick <idr>
Status: CLOSED WONTFIX QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium CC: eero.t.tamminen, jianx.zhou
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description meng 2014-03-20 11:10:24 UTC 
System Environment:
--------------------------
Mesa:   (master)eaf9affa5ec9c5fd919e4207ab80b4677650ac67
Xserver:(master)xorg-server-1.15.99.901 Xf86_video_intel:	
Xf86_video_intel:(master)2.99.911
Kernel:	(drm-intel-nightly)git-ec45c7

Bug detailed description:
----------------------------
It’s not a regression, firstly test ogl-samples.

Pre-conditions:
 - build: https://github.com/g-truc/ogl-samples

Test-case: gl-320-glsl-cast-fail

Actual outcome:
------------------------
- doesn't run
- "0:24(19): error: syntax error, unexpected LOWP"
Comment 1 Kenneth Graunke 2014-03-23 08:53:26 UTC 
This is the failing line:

    lowp int Count = lowp int(COUNT);

I really hope that's not legal syntax for casting...definitely not excited about constructors with spaces in their name.  Then again, I don't know what the syntax would be...
Comment 2 Eero Tamminen 2014-03-24 10:37:19 UTC 
Looking at the commit message adding this test "..added 320-glsl-cast and input-struct fail tests..." I wonder whether these two tests are supposed to fail.  The name of this tests indicates it, but it's a bit weird why the test doesn't check that operation fails, and then report success for the failure test.

(Maybe glslangValidator.exe from ogl-samples does that on Windows.)
Comment 3 Ian Romanick 2014-12-17 19:44:29 UTC 
(In reply to Kenneth Graunke from comment #1)
> This is the failing line:
> 
>     lowp int Count = lowp int(COUNT);

This is not valid syntax in any version of GLSL.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.