Fix assertion failure in dfdx and dfdy lost bit calculations.
authorJarkko Pöyry <jpoyry@google.com>
Thu, 12 Mar 2015 20:17:38 +0000 (13:17 -0700)
committerJarkko Pöyry <jpoyry@google.com>
Thu, 12 Mar 2015 21:17:55 +0000 (14:17 -0700)
commitd9551dc8ecff19b0bfe50e0a463c49e99997b4a2
tree212e87c89b5f68015b1db70232767445fa5f6d1f
parent6476d819be75d7dae16a262620d16f13d4f2233c
Fix assertion failure in dfdx and dfdy lost bit calculations.

- Fix lost-bits calculation returning negative values when operand
  component range intercepted zero (i.e. operands had different signs).
  This caused verification to expect more significant bits than the
  native (lowp/mediump/highp) float format could store. With highp
  values, error calculation tried to create a error compontent of a
  floating point value with 24 mantissa bits which cannot be stored
  to a native float32.
- Use better terminology, s/nominator/numerator/.

Bug: 19694789
Change-Id: Ifa88fb1c8cb333bab22a550d01f5e310d2d2673d
modules/gles3/functional/es3fShaderDerivateTests.cpp