Bug 80836

Summary: [llvmpipe] [softpipe] piglit incorrect-in-layout-qualifier-repeated-prim.geom regression
Product: Mesa Reporter: Vinson Lee <vlee>
Component: Mesa coreAssignee: mesa-dev
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: medium CC: idr, siglesias
Version: gitKeywords: bisected, regression
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Vinson Lee 2014-07-03 00:39:07 UTC
mesa: 6ded75ed08aed8a88b638c664efbfe14e0476f37 (master 10.3.0-devel)

$ ./bin/glslparsertest tests/spec/glsl-1.50/compiler/incorrect-in-layout-qualifier-repeated-prim.geom fail 1.50
Successfully compiled geometry shader tests/spec/glsl-1.50/compiler/incorrect-in-layout-qualifier-repeated-prim.geom: 
Shader source:
// [config]
// expect_result: fail
// glsl_version: 1.50
// check_link: false
// [end config]
//
// Tests for invalid input layout qualifiers.
//
// GLSLangSpec 1.50, section 4.3.8.1 (Input Layout Qualifiers):
// "Only one argument is accepted. For example,
//  layout(triangles) in;"
//

#version 150

layout(points, points) in;

void main()
{
}

PIGLIT: {"result": "fail" }



a7e6ec68985dda9ca70c3eeb4fa9d807b67f7c99 is the first bad commit
commit a7e6ec68985dda9ca70c3eeb4fa9d807b67f7c99
Author: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
Date:   Tue Jun 10 08:45:43 2014 +0200

    glsl: Add parsing support for multi-stream output in geometry shaders.
    
    This implements parsing requirements for multi-stream support in
    geometry shaders as defined in ARB_gpu_shader5.
    
    Signed-off-by: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
    Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>

:040000 040000 41fe3b6baf4ff1bf5b30e2cde472315069cfa175 b98a4a332055cd4ffd24d5a951c3fc61db421e1e M	src
bisect run success
Comment 1 Samuel Iglesias Gonsálvez 2014-07-03 06:01:51 UTC

*** This bug has been marked as a duplicate of bug 80778 ***

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.