Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd initial support for VertexAttribI4* and VertexAttribIPointer #26123
Conversation
highfive
commented
Apr 6, 2020
|
Heads up! This PR modifies the following files:
|
highfive
commented
Apr 6, 2020
|
Thanks for implementing this! |
|
|
||
| let current_vertex_attrib = | ||
| self.base.current_vertex_attribs()[prog_attrib.location as usize]; | ||
| let attrib_data_base_type = if attrib.enabled_as_array { |
This comment has been minimized.
This comment has been minimized.
jdm
Apr 6, 2020
Member
This check looks backward to me, and when I invert it then all the test failures in attrib-type-match.html and gl-vertex-attrib-i-render.html disappear for me.
This comment has been minimized.
This comment has been minimized.
imiklos
Apr 7, 2020
Author
Contributor
Thank you! You are right! I've updated the test expectations but the test failures did not disappear on my side. Could it be driver related?
|
I agree with you that the assert for glGetFragDataLocation should be removed. |
Adds initial support for the WebGL2 `VertexAttribI4i`, `VertexAttribI4iv`, `VertexAttribI4ui`, `VertexAttribI4uiv` and `VertexAttribIPointer` calls.
|
@jdm Thank you for the review! I've removed the assert from the |
|
@bors-servo try=wpt |
Add initial support for VertexAttribI4* and VertexAttribIPointer Add initial support for the WebGL2 `VertexAttribI4i`, `VertexAttribI4iv`, `VertexAttribI4ui`, `VertexAttribI4uiv` and `VertexAttribIPointer` calls. <!-- Please describe your changes on the following line: --> I've already updated the test expectations and noticed that I've got a crash on the `conformance2/state/gl-object-get-calls.html` test, which is related to the `GetFragDataLocation`. The crash comes from here: https://github.com/servo/servo/blob/b4d7ec1c99259f936c9e34de157b652707d308de/components/canvas/webgl_thread.rs#L1292 The assert is invalid here because the `GetFragDataLocation` GL call could return with `-1` also. (https://www.khronos.org/registry/OpenGL-Refpages/es3.0/html/glGetFragDataLocation.xhtml) --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [X] There are tests for these changes cc @mmatyas @zakorgy @jdm <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
|
The GetActiveUniformBlockName panic is caused by #26134. |
Add initial support for VertexAttribI4* and VertexAttribIPointer Add initial support for the WebGL2 `VertexAttribI4i`, `VertexAttribI4iv`, `VertexAttribI4ui`, `VertexAttribI4uiv` and `VertexAttribIPointer` calls. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #26134 and fix #26123. - [x] There are tests for these changes
Add initial support for VertexAttribI4* and VertexAttribIPointer Add initial support for the WebGL2 `VertexAttribI4i`, `VertexAttribI4iv`, `VertexAttribI4ui`, `VertexAttribI4uiv` and `VertexAttribIPointer` calls. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #26134 and fix #26123. - [x] There are tests for these changes
imiklos commentedApr 6, 2020
Add initial support for the WebGL2
VertexAttribI4i,VertexAttribI4iv,VertexAttribI4ui,VertexAttribI4uivandVertexAttribIPointercalls.I've already updated the test expectations and noticed that I've got a crash on the
conformance2/state/gl-object-get-calls.htmltest, which is related to theGetFragDataLocation.The crash comes from here:
servo/components/canvas/webgl_thread.rs
Line 1292 in b4d7ec1
The assert is invalid here because the
GetFragDataLocationGL call could return with-1also. (https://www.khronos.org/registry/OpenGL-Refpages/es3.0/html/glGetFragDataLocation.xhtml)./mach build -ddoes not report any errors./mach test-tidydoes not report any errorscc @mmatyas @zakorgy @jdm