<div dir="ltr">On Tue, Apr 30, 2013 at 8:33 PM, Geoffrey Garen <span dir="ltr"><<a href="mailto:ggaren@apple.com" target="_blank">ggaren@apple.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><blockquote type="cite">
<div dir="ltr"><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">Over the past weeks, some discussion involving WebCL took place in this mailing list ([2]), when some concerns were raised, and to which I later on tried to address in [3].</div>
</div></blockquote><div><br></div></div>I believe your answer in [3] to the security problems posed by WebCL was that a standards group is working on a security specification, which future GPUs might implement. Do any GPUs implement that specification?</div>
<div><br></div></div></blockquote><div><br></div><div>Hi Geoff.</div><div><br></div><div>It is chicken-egg problem: without Browser vendors commitment to WebCL, the motivation for hardware vendors to implement, for example, OpenCL 1.2 "Memory Initialization" and "Context termination" extensions, required by WebCL, is not as strong.</div>
<div><br></div><div>
--Antonio</div></div></div></div>