W3C home > Mailing lists > Public > public-gpu@w3.org > November 2018

Re: draft execution environment for WebGPU, including WebGPU env spec for SPIR-V

From: Maciej Stachowiak <mjs@apple.com>
Date: Tue, 13 Nov 2018 15:05:10 -0800
Message-id: <84C8C9B0-EBDE-4B34-8793-59EC6326F716@apple.com>
Cc: public-gpu <public-gpu@w3.org>
To: David Neto <dneto@google.com>

This document describes what security properties are desired In the "General WebGPU Environment” section, which is great. But it doesn’t appear to describe how a SPIR-V dialect can achieve these properties in the "WebGPU Execution Environment Specification for SPIR-V”, not even as TBDs as far as I can tell.

Is it it intentional that how to achieve security is unspecified?


> On Nov 13, 2018, at 1:41 PM, David Neto <dneto@google.com> wrote:
> Hi,
> In a recent meeting Google promised to produce a draft WebGPU environment spec for SPIR-V. 
> Today we created a new GitHub repo for all documents related to SPIR-V use in WebGPU.  It has a first draft of the promised environment spec.  Please see https://github.com/gpuweb/spirv-execution-env/blob/master/execution-env.md <https://github.com/gpuweb/spirv-execution-env/blob/master/execution-env.md>
> In writing the draft we realized there were considerations on how WebGPU would execute shaders, independent of shader language. So the document is split in to several parts: A general part that always would apply, and a part that is a WebGPU environment spec for SPIR-V.
> Many items are marked "TBD", and most of them will be resolved once the community group determines exactly what features are supported by WebGPU.
> This is ready for initial review and discussion by the community group.
> thanks,
> david

Received on Tuesday, 13 November 2018 23:05:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:52:25 UTC