[Bug 95242] piglit.spec.arb_separate_shader_objects.execution.layout-location-named-block regression
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon May 2 18:38:29 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=95242
Bug ID: 95242
Summary: piglit.spec.arb_separate_shader_objects.execution.layo
ut-location-named-block regression
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/i965
Assignee: idr at freedesktop.org
Reporter: mark.a.janes at intel.com
QA Contact: intel-3d-bugs at lists.freedesktop.org
mesa 0d88b15f073d09afed1747d9cdde98f15c7aa28d regressed this test:
Standard Output
/tmp/build_root/m64/lib/piglit/bin/shader_runner
/tmp/build_root/m64/lib/piglit/tests/spec/arb_separate_shader_objects/execution/layout-location-named-block.shader_test
-auto
piglit: debug: Requested an OpenGL 3.2 Core Context, and received a matching
3.3 context
Standard Error
Failed to link:
error: fragment shader input `name2' with explicit location has no matching
output
error: fragment shader input `name' with explicit location has no matching
output
------------------------------------------------------------
Author: Timothy Arceri <timothy.arceri at collabora.com>
glsl: cross validate varyings with a component qualifier
This change checks for component overlap, including handling overlap of
locations and components by doubles. Previously there was no validation
for assigning explicit locations to a location used by the second half
of a double.
V3: simplify handling of doubles and fix double component aliasing
detection
V2: fix component matching for matricies
Reviewed-by: Anuj Phogat <anuj.phogat at gmail.com>
Reviewed-by: Edward O'Callaghan <eocallaghan at alterapraxis.com>
Reviewed-by: Kenneth Graunke <kenneth at whitecape.org>
--
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/20160502/59bf6f5a/attachment.html>
More information about the intel-3d-bugs
mailing list