On 02/22/2013 04:44 PM, Jonathan Hamilton wrote:
Hi all,
I have an issue where an ARBfp shader does the following:
"""
!!ARBfp1.0
OPTION ARB_precision_hint_fastest;
OPTION ARB_precision_hint_fastest;
"""
This is then being rejected by the mesa parser.
The spec I found at
http://oss.sgi.com/projects/ogl-sample/registry/ARB/fragment_program.txt says
"Only one precision control option may be specified by any given
fragment program.", but that seems to be unclear if you are only
specifying one of the options multiple times.
Can anyone help clarify is this is a bug in mesa, or the application?
Either way, since drivers implementing this behavior exist on a large
number of systems, the path of least resistance is probably to change
the application.
Thanks,
Jonathan Hamilton
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
