News for hackers. Stuff that matters.

A comment on Chrome dev on WebGL security and Microsoft bullshit.

Re:Chrome dev on WebGL security and Microsoft bullshit by twp on Tuesday June 21, 2011 @07:34AM (#2678298)
From the article:

"[The GPU process] validates that the shaders submitted to the GPU use only the minimal features allowed by the spec. That means no dynamic indexing of sampler arrays. It means no infinite loops."

Halting problem solved. News at 11 :-)

[ Parent | on HN ]
Re:Chrome dev on WebGL security and Microsoft bullshit by masklinn on Tuesday June 21, 2011 @07:39AM (#2678312)
> Halting problem solved. News at 11 :-)

Not necessarily, WebGL could simply restrict the shaders language to not be turing-complete. No need for solving the halting problem if you start from a total language.

[ Parent | on HN ]
Re:Chrome dev on WebGL security and Microsoft bullshit by magicalist on Tuesday June 21, 2011 @05:16PM (#2680458)
yep. because webgl is designed to work on platforms that may have to fully unroll loops in shaders (because of its mobile baseline), webgl shaders are not turing complete in and of themselves.
[ Parent | on HN ]