| Summary: |
Getting different output depending on attribute declaration order |
| Product: |
Mesa
|
Reporter: |
Neha Bhende <bhenden> |
| Component: |
glsl-compiler | Assignee: |
mesa-dev |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: |
major
|
|
|
| Priority: |
medium
|
|
|
| Version: |
git | |
|
| Hardware: |
All | |
|
| OS: |
Linux (All) | |
|
| Whiteboard: |
|
|
i915 platform:
|
|
i915 features:
|
|
|---|
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.
I am getting different results depending on attribute order. For example, in piglit test gl-2.0-vertex-const-attr, vertex shader has attribute order as "attribute vec2 vertex; \n" "attribute vec4 attr; \n" If I modified it to "attribute vec4 attr; \n" "attribute vec2 vertex; \n" I am getting wrong results. If I bind attributes to particular location using glBindAttribLocation call then it works fine. If I use glGetAttribLocation to get corresponding attribute location, then it gives wrong results.