On Wed, May 1, 2013 at 8:41 PM, Oliver Hunt wrote:
>
> On May 1, 2013, at 5:29 PM, Antonio Gomes wrote:
>
> - 4.3 Out-of-Range Memory Access
>
> The validator will perform static analysis on WebCL kernels to
> determine violations of WebCL kernel behavior and language restrictions.
> The results
On May 1, 2013, at 5:29 PM, Antonio Gomes wrote:
> - 4.2 Cross-Origin Information Leakage
> WebCL's position is that this be handled by the same mechanism as used for
> WebGL, ie https://www.khronos.org/registry/webgl/specs/latest/#4.2 . A bug
> will be filed to request update of wording in the
On Tue, Apr 30, 2013 at 8:33 PM, Geoffrey Garen wrote:
> 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].
>
>
> I believe your answer in [3] to the security problems pos
On Tue, Apr 30, 2013 at 8:14 PM, Benjamin Poulain wrote:
> On Tue, Apr 30, 2013 at 5:10 PM, Antonio Gomes wrote:
>
>> At this time, I would like to contribute our WebCL prototype
>> implementation [4] to WebKit.org.
>>
>> Feature would be defined behind a ENABLE(WEBCL) feature flag, and work
>> wi
Hi Oliver. Thanks for your comments and suggestions. Here's an update on
WebCL security.
First some background: within Khronos a cross working group security
initiative was started by the WebCL working group to engage with the
OpenCL, WebGL, OpenGL and OpenGL-ES working groups and representatives
While investigating a crash in the 'create-lots-of-workers' test (see
https://bugs.webkit.org/show_bug.cgi?id=115130), I found that there were a
number of cases where objects were created using the system allocator, but
later freed using the 'fastFree' overload provided by fastMalloc.h.
I proposed
6 matches
Mail list logo
