commit | 3de2703d83bf9f3747e6f80d98e3ab70ea1ba5e8 | [log] [tgz] |
---|---|---|
author | Olli Etuaho <oetuaho@nvidia.com> | Thu Nov 30 10:16:47 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Dec 04 20:31:47 2017 |
tree | f03e6b0725692e0550e008cb08906c9f6c4b1ee6 | |
parent | bf0a40bbcd6ef80e77073f641d4d9f9817908eeb [diff] |
Fix handling matrix qualifiers on block members Individual block member row_major/column_major layout qualifiers may override the qualifiers set on the block. During parsing, this was already being handled correctly, so that the qualifier is resolved for each block member and recorded for each TField / InterfaceBlockField. Now we always write the qualifiers on a per-member granularity to the output GLSL shaders, so that the native driver gets the correct per-member qualifiers. This replaces earlier behavior where the matrix qualifiers were only written per-block. Also only use qualifiers from individual members in block layout. Since the block-level qualifier information is no longer used after parsing, it is no longer kept in the AST. A dummy value is still set to the InterfaceBlock structs exposed through the ShaderVars interface, since that has existing usage in Chromium that needs to be removed before the field can be removed. Some AMD OpenGL drivers don't seem to handle matrix layout qualifiers correctly, so most of the added tests need to be skipped for AMD GL. On NVIDIA and Intel the tests pass. BUG=angleproject:2271 TEST=angle_unittests, angle_end2end_tests, dEQP-GLES31.functional.program_interface_query.uniform.matrix* Change-Id: I1baa7a633bc2da548743c2190cb72db491b5227a Reviewed-on: https://chromium-review.googlesource.com/800174 Reviewed-by: Jamie Madill <jmadill@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Olli Etuaho <oetuaho@nvidia.com>
The goal of ANGLE is to allow users of multiple operating systems to seamlessly run WebGL and other OpenGL ES content by translating OpenGL ES API calls to one of the hardware-supported APIs available for that platform. ANGLE currently provides translation from OpenGL ES 2.0 and 3.0 to desktop OpenGL, OpenGL ES, Direct3D 9, and Direct3D 11. Support for translation from OpenGL ES to Vulkan is underway, and future plans include compute shader support (ES 3.1) and MacOS support.
Direct3D 9 | Direct3D 11 | Desktop GL | GL ES | Vulkan | |
---|---|---|---|---|---|
OpenGL ES 2.0 | complete | complete | complete | complete | in progress |
OpenGL ES 3.0 | complete | complete | in progress | not started | |
OpenGL ES 3.1 | not started | in progress | in progress | not started |
Direct3D 9 | Direct3D 11 | Desktop GL | GL ES | Vulkan | |
---|---|---|---|---|---|
Windows | complete | complete | complete | complete | in progress |
Linux | complete | planned | |||
Mac OS X | in progress | ||||
Chrome OS | complete | planned | |||
Android | complete | planned |
ANGLE v1.0.772 was certified compliant by passing the ES 2.0.3 conformance tests in October 2011. ANGLE also provides an implementation of the EGL 1.4 specification.
ANGLE is used as the default WebGL backend for both Google Chrome and Mozilla Firefox on Windows platforms. Chrome uses ANGLE for all graphics rendering on Windows, including the accelerated Canvas2D implementation and the Native Client sandbox environment.
Portions of the ANGLE shader compiler are used as a shader validator and translator by WebGL implementations across multiple platforms. It is used on Mac OS X, Linux, and in mobile variants of the browsers. Having one shader validator helps to ensure that a consistent set of GLSL ES shaders are accepted across browsers and platforms. The shader translator can be used to translate shaders to other shading languages, and to optionally apply shader modifications to work around bugs or quirks in the native graphics drivers. The translator targets Desktop GLSL, Direct3D HLSL, and even ESSL for native GLES2 platforms.
ANGLE repository is hosted by Chromium project and can be browsed online or cloned with
git clone https://chromium.googlesource.com/angle/angle
View the Dev setup instructions. For generating a Windows Store version of ANGLE view the Windows Store instructions
Join our Google group to keep up to date.
Join us on IRC in the #ANGLEproject channel on FreeNode.
File bugs in the issue tracker (preferably with an isolated test-case).
Choose an ANGLE branch to track in your own project.
Read ANGLE development documentation.
Become a code contributor.
Use ANGLE's coding standard.
Learn how to build ANGLE for Chromium development.
Get help on debugging ANGLE.
Read about WebGL on the Khronos WebGL Wiki.
Learn about implementation details in the OpenGL Insights chapter on ANGLE and this ANGLE presentation.
Learn about the past, present, and future of the ANGLE implementation in this recent presentation.
If you use ANGLE in your own project, we'd love to hear about it!