Range check transfer params in float domain
Our native code uses floats for transfer parameters, the range check was too small (using the next representable double instead of the next representable float). Bug: 37013532 Test: Manual run of broken app, CtsGraphicsTestCases Change-Id: Id91a3e62068be0abf13ee75e39c758eb106a5f24 (cherry picked from commit bfa58aab)
Loading
Please register or sign in to comment