- From: Jeff Gilbert <jgilbert@mozilla.com>
- Date: Wed, 16 Aug 2017 17:08:03 -0700
- To: Dean Jackson <dino@apple.com>
- Cc: Maciej Stachowiak <mjs@apple.com>, Kenneth Russell <kbr@google.com>, Corentin Wallez <cwallez@google.com>, David Neto <dneto@google.com>, "Myles C. Maxfield" <mmaxfield@apple.com>, public-gpu@w3.org
Vulkan requires logical addressing mode for all shaders, including compute: https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#spirvenv-module-validation On Wed, Aug 16, 2017 at 4:39 PM, Dean Jackson <dino@apple.com> wrote: > > > On 17 Aug 2017, at 05:08, Maciej Stachowiak <mjs@apple.com> wrote: > > But bolting on security is not impossible; as you point out, it's been done > for GLSL. > > > Restricting GLSL for security wasn't particularly difficult. It doesn't have > pointers, for example. This is another argument for a language that is > slightly higher than an IR: It probably will be easier to secure. > > For the SPIR-V folks, has any implementation actually used Logical > Addressing Mode? I'd also like to understand what these proposed > restrictions to SPIR-V mean for compute shaders. How are they impacted by > Logical Addressing Mode? > > Dean >
Received on Thursday, 17 August 2017 00:08:29 UTC