Native APIs specify the valid usage for the commands CPU-based undefined behaviorĪ WebGPU implementation translates the workloads issued by the user into API commands specific The general approach is strictly validating all the commands before they reach GPU,Įnsuring that a page can only work with its own data. The security requirements for WebGPU are the same as ever for the web, and are likewise non-negotiable. It describes the risks associated with exposing this API on the Web. Such as beginRenderPass() or setBlendConstant(). In these pipeline objects is set during encoding with commands, Most of the state of a pipeline is defined byĪ GPURenderPipeline or a GPUComputePipeline object. Programmable stages execute shaders, which are special programs designed to run on GPU hardware.
Which is a mix of fixed-function and programmable stages. GPUs execute commands encoded in GPUCommandBuffers by feeding data through a pipeline, Such as GPUSampler or GPUBindGroup, configure the way physical resources are used by the GPU. GPUCommandBuffer and GPURenderBundle are containers for user-recorded commands. GPUBuffer and GPUTexture are the physical resources backed by GPU memory. GPUDevice may have its own memory with high-speed access to the processing units. It provides a connection to an adapter via GPUDevice, which manages resources, and the device’s GPUQueues, which execute commands. WebGPU sees physical GPU hardware as GPUAdapters. WebGPU is not related to WebGL and does not explicitly target OpenGL ES. The API is designed from the ground up to efficiently map to (post-2014) native GPU APIs. WebGPU is an API that exposes the capabilities of GPU hardware for the Web. Have been essential in enabling rich rendering and computational applications in personal computing. Graphics Processing Units, or GPUs for short, 26.1.2.2 Copying Depth/Stencil Textures.26.1.2.1 Reading and Sampling Depth/Stencil Textures.9.1.2 Shader Module Compilation Information.9.1.1.1 Shader Module Compilation Hints.3.11 Numeric conversions from JavaScript to WGSL.3.2.1 Invalid Internal Objects & Contagious Invalidity.2.2.1 Machine-specific features and limits.This document is governed by the 2 November 2021 W3C Process Document. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group that page also includes instructions for disclosing a patent. This document was produced by a group operating under the W3C Patent Policy. It is inappropriate to cite this document as other than work in progress. This is a draft document and may be updated, replaced or obsoleted by other documents at any time.
Publication as a Working Draft does not imply endorsement by W3C and its Members. This document is intended to become a W3C Recommendation.
This document was published by the GPU for the Web Working Group as a Working Draft using the Recommendation No decision has been taken on the outcome of these issues including whether they are valid. This draft highlights some of the pending issues that are still to be discussed in the working group. Alternatively, you can send comments to the GPU for the Web Working Group’s mailing-list, ( archives). GitHub Issues are preferred for discussion on this specification. įeedback and comments on this specification are welcome. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at. This section describes the status of this document at the time of its publication.
0 kommentar(er)
