search

BlamKiwi / angleproject

Automatically exported from code.google.com/p/angleproject
Other
0 stars 0 forks source link

GL_FRAGMENT_PRECISION_HIGH support in ES3 #1039

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It looks like we should pre-process GL_FRAGMENT_PRECISION_HIGH in ES3 shader 
translator.  Otherwise a shader ported from ES2 using 
GL_FRAGMENT_PRECISION_HIGH may end up falling back to mediump, whereas highp is 
always supported in ES3.

Original issue reported on code.google.com by zmo@chromium.org on 5 Jun 2015 at 6:47

GoogleCodeExporter commented 9 years ago

Original comment by z...@google.com on 5 Jun 2015 at 6:47

GoogleCodeExporter commented 9 years ago 
This is not in the spec, but it does seem like a good idea if we want to make 
content bugs more harmless. Maybe ANGLE could issue a warning when 
GL_FRAGMENT_PRECISION_HIGH is used in an ES3 shader as well?

Original comment by oetu...@nvidia.com on 8 Jun 2015 at 8:13

GoogleCodeExporter commented 9 years ago 
Now I think about it, a warning to the program log should be a better solution. 
We could probably allow translator to set a warning bit, so chrome can wire the 
warning log to js console.

Original comment by z...@google.com on 8 Jun 2015 at 10:40