commit | 968041b54770af8917001d8fe9b52a881cfed0b2 | [log] [tgz] |
---|---|---|
author | Gregg Tavares <gman@chromium.org> | Fri Aug 19 12:11:23 2022 -0700 |
committer | Angle LUCI CQ <angle-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 18 00:09:11 2022 +0000 |
tree | 2ab30a1fa31c82d78f4e802a8c7fbc0682175cce | |
parent | 0e0ea0265bf8faa41adda42e45a728924bd1bad8 [diff] |
Metal: Optimized BufferSubData per device Adds a staging buffer path which means there are 4 paths for bufferSubData. 1. direct copy * get a pointer to the buffer * copy the new data to the buffer * if the buffer is managed, tell metal which part was updated 2. use a shadow copy * copy the data to a shadow copy * copy the entire shadow to a new buffer * start using the new buffer 3. use a new buffer * get a new buffer (or unused) * put the new data in the new buffer * blit any unchanged data from the old buffer to the new buffer * start using the new buffer 4. use a staging buffer * get a staging buffer * put the new data in the staging buffer * blit from the staging buffer to the existing buffer. Further, there are 3 types of memory storage modes. Managed, Staged, Private. Based on the GPU type different storage modes and different paths in different sitatutions are more performant. So, add feature flags to select paths by GPU. Bug: angleproject:7544 Change-Id: I741dd1874201043416374194bd2001ded8dbd9b4 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/3842641 Reviewed-by: Kyle Piddington <kpiddington@apple.com> Reviewed-by: Kenneth Russell <kbr@chromium.org> Reviewed-by: Quyen Le <lehoangquyen@chromium.org> Commit-Queue: Gregg Tavares <gman@chromium.org>
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, 3.0 and 3.1 to Vulkan, desktop OpenGL, OpenGL ES, Direct3D 9, and Direct3D 11. Future plans include ES 3.2, translation to Metal and MacOS, Chrome OS, and Fuchsia support.
Direct3D 9 | Direct3D 11 | Desktop GL | GL ES | Vulkan | Metal | |
---|---|---|---|---|---|---|
OpenGL ES 2.0 | complete | complete | complete | complete | complete | complete |
OpenGL ES 3.0 | complete | complete | complete | complete | in progress | |
OpenGL ES 3.1 | incomplete | complete | complete | complete | ||
OpenGL ES 3.2 | in progress | in progress | in progress |
Direct3D 9 | Direct3D 11 | Desktop GL | GL ES | Vulkan | Metal | |
---|---|---|---|---|---|---|
Windows | complete | complete | complete | complete | complete | |
Linux | complete | complete | ||||
Mac OS X | complete | in progress | ||||
iOS | in progress | |||||
Chrome OS | complete | planned | ||||
Android | complete | complete | ||||
GGP (Stadia) | complete | |||||
Fuchsia | complete |
ANGLE v1.0.772 was certified compliant by passing the OpenGL ES 2.0.3 conformance tests in October 2011.
ANGLE has received the following certifications with the Vulkan backend:
ANGLE also provides an implementation of the EGL 1.5 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, Vulkan 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.
Join our Google group to keep up to date.
Join us on Slack in the #angle channel. You can follow the instructions on the Chromium developer page for the steps to join the Slack channel. For Googlers, please follow the instructions on this document to use your google or chromium email to join the Slack channel.
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.
Go through ANGLE's orientation and sift through starter projects. If you decide to take on any task, write a comment so you can get in touch with us, and more importantly, set yourself as the “owner” of the bug. This avoids having multiple people accidentally working on the same issue.
Read about WebGL on the Khronos WebGL Wiki.
Learn about the initial ANGLE implementation details in the OpenGL Insights chapter on ANGLE (this is not the most up-to-date ANGLE implementation details, it is listed here for historical reference only) and this ANGLE presentation.
Learn about the past, present, and future of the ANGLE implementation in this presentation.
Watch a short presentation on the Vulkan back-end.
Track the dEQP test conformance
Read design docs on the Vulkan back-end
Read about ANGLE's testing infrastructure
View information on ANGLE's supported extensions
If you use ANGLE in your own project, we'd love to hear about it!