[go: up one dir, main page]
Google Git
Sign in
chromium / angle / angle / refs/heads/chromium/7485
commit058ca0117f6fd9a51974dab8f7224d9bc7a7ffef[log] [tgz]
authorAmirali Abdolrashidi <abdolrashidi@google.com>Fri Oct 03 22:58:17 2025
committerAngle LUCI CQ <angle-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Oct 20 19:24:45 2025
tree8033f001ec20603ee182e84909bb6756c84de568
parent269785112c31affb3d31db5764bad450f3735758 [diff]
Mark buffer as dirty with size change

  When binding vertex buffers, dirty bits for the buffer can be set
in case of change in offset, stride, or buffer handle. However, it
is not set when buffer size changes. This can cause an outdated size
to be used for vertex array parameters if other parameters remain
the same (e.g., mCurrentArrayBufferSizes in VertexArrayVk), which
could result in wrong output).

* Replaced mBufferAccessValidationEnabled to mRobustBufferAccessEnabled
  in VertexArray.
  * This flag is enabled if the context has robust access or if it is
    WebGL, regardless of the robust buffer access behavior extension.

* New bit (DIRTY_BINDING_SIZE) is set in the vertex array dirty binding
  bits when the bound buffer size is not the same as the cached buffer
  size.
  * updateBindingSizeIfChanged()

* Added test in RobustBufferAccessBehaviorTest for buffer size change.
  * ChangeBufferDataSizeWithSameAttribPointer
    * Inspired by the code from the following dEQP test:
      dEQP-GLES3.functional.buffer.write.recreate_store.different_size

* For BindVertexBuffers2(), pSizes is only added if robust access is
  enabled or if it is forced for testing. Otherwise, nullptr is used.
  * Using the new feature flag forceSizePointerForBoundVertexBuffers.
    * It is enabled when syncval is enabled and BindVertexBuffers2 is
      supported.
    * It is force-disabled on some vertex attribute tests for testing
      to test with the null size pointer even if validation is enabled.

* Moved the syncval suppressions related to vertex attributes to a new
  array: kSkippedSyncvalMessagesWithoutForcedSizePointer
  * (VK_ACCESS_2_VERTEX_ATTRIBUTE_READ_BIT)
  * These suppressions are only added if the feature flag above is
    disabled.

Bug: angleproject:448047351
Bug: angleproject:394598470
Bug: angleproject:443095908
Bug: angleproject:397775556
Bug: angleproject:42264123
Bug: angleproject:42266180
Bug: angleproject:42266309
Change-Id: I686cc24d283d0295990445c5b82cd05b54315fb0
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/7009068
Reviewed-by: Charlie Lao <cclao@google.com>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Commit-Queue: Amirali Abdolrashidi <abdolrashidi@google.com>
18 files changed
tree: 8033f001ec20603ee182e84909bb6756c84de568
  1. android/
  2. build_overrides/
  3. doc/
  4. extensions/
  5. gni/
  6. include/
  7. infra/
  8. samples/
  9. scripts/
  10. src/
  11. third_party/
  12. tools/
  13. util/
  14. build
  15. buildtools
  16. testing
  17. .clang-format
  18. .clang-format-ignore
  19. .git-blame-ignore-revs
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .gn
  24. .style.yapf
  25. .vpython
  26. .vpython3
  27. .yapfignore
  28. additional_readme_paths.json
  29. Android.mk
  30. AUTHORS
  31. BUILD.gn
  32. codereview.settings
  33. CONTRIBUTORS
  34. DEPS
  35. DIR_METADATA
  36. dotfile_settings.gni
  37. LICENSE
  38. OWNERS
  39. PRESUBMIT.py
  40. README.chromium
  41. README.md
  42. unsafe_buffers_paths.txt
  43. WATCHLISTS
README.md

ANGLE - Almost Native Graphics Layer Engine

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.

Level of OpenGL ES support via backing renderers

Direct3D 9Direct3D 11Desktop GLGL ESVulkanMetal
OpenGL ES 2.0completecompletecompletecompletecompletecomplete
OpenGL ES 3.0completecompletecompletecompletecomplete
OpenGL ES 3.1incompletecompletecompletecomplete
OpenGL ES 3.2in progressin progresscomplete

Additionally, OpenGL ES 1.1 is implemented in the front-end using OpenGL ES 3.0 features. This version of the specification is thus supported on all platforms specified above that support OpenGL ES 3.0 with known issues.

Platform support via backing renderers

Direct3D 9Direct3D 11Desktop GLGL ESVulkanMetal
Windowscompletecompletecompletecompletecomplete
Linuxcompletecomplete
Mac OS Xcompletecomplete [1]
iOScomplete [2]
Chrome OScompleteplanned
Androidcompletecomplete
Fuchsiacomplete

[1] Metal is supported on macOS 10.14+

[2] Metal is supported on iOS 12+

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:

  • OpenGL ES 2.0: ANGLE 2.1.0.d46e2fb1e341 (Nov, 2019)
  • OpenGL ES 3.0: ANGLE 2.1.0.f18ff947360d (Feb, 2020)
  • OpenGL ES 3.1: ANGLE 2.1.0.f5dace0f1e57 (Jul, 2020)
  • OpenGL ES 3.2: ANGLE 2.1.2.21688.59f158c1695f (Sept, 2023)

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.

OpenCL Implementation

In addition to OpenGL ES, ANGLE also provides an optional OpenCL runtime built into the same output GLES lib.

This work/effort is currently work-in-progress/experimental.

This work provides the same benefits as the OpenGL implementation, having OpenCL APIs be translated to other HW-supported APIs available on that platform.

Level of OpenCL support via backing renderers

VulkanOpenCL
OpenCL 1.0in progressin progress
OpenCL 1.1in progressin progress
OpenCL 1.2in progressin progress
OpenCL 3.0in progressin progress

Each supported backing renderer above ends up being an OpenCL Platform for the user to choose from.

The OpenCL backend is a “passthrough” implementation which does not perform any API translation at all, instead forwarding API calls to other OpenCL driver(s)/implementation(s).

OpenCL also has an online compiler component to it that is used to compile OpenCL C source code at runtime (similarly to GLES and GLSL). Depending on the chosen backend(s), compiler implementations may vary. Below is a list of renderers and what OpenCL C compiler implementation is used for each:

  • Vulkan : clspv
  • OpenCL : Compiler is part of the native driver

Sources

ANGLE repository is hosted by Chromium project and can be browsed online or cloned with

git clone https://chromium.googlesource.com/angle/angle

Building

View the Dev setup instructions.

Contributing