gpu: Workaround invalid values from GetShaderPrecisionFormat
commit448e459e5cde2a4b6844bd51c478167ad0ba2c78
authorbrianderson@chromium.org <brianderson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 12 Jun 2013 17:00:41 +0000 (12 17:00 +0000)
committerbrianderson@chromium.org <brianderson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 12 Jun 2013 17:00:41 +0000 (12 17:00 +0000)
tree0546e4de8d23b2900368691b35272d474b922fde
parentf33ad01a701cd61dac938d2069b9f32b3fbe9dac
gpu: Workaround invalid values from GetShaderPrecisionFormat

N4 reports negative numbers in the range when they should be positive,
so we take the absolute value of the range before sending it to the
client.

Some devices report highp precisions when they can't actually be used,
so we force highp precisions to 0 (usupported) in those cases before
sending it to the client.

BUG=245755

Review URL: https://chromiumcodereview.appspot.com/16409014

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205832 0039d316-1c4b-4281-b951-d872f2087c98
gpu/command_buffer/service/gles2_cmd_decoder.cc