Do not require signed zero support in frexp() tests

Bug: 25933766
Change-Id: Ided7abef00010b97133f79930f6edcd73333c5ed

diff --git a/modules/gles31/functional/es31fShaderCommonFunctionTests.cpp b/modules/gles31/functional/es31fShaderCommonFunctionTests.cpp
index aafd861..40cd452 100644 (file)
--- a/modules/gles31/functional/es31fShaderCommonFunctionTests.cpp
+++ b/modules/gles31/functional/es31fShaderCommonFunctionTests.cpp
@@ -1795,8 +1795,7 @@ public:
                const glu::DataType             type                                            = m_spec.inputs[0].varType.getBasicType();
                const glu::Precision    precision                                       = m_spec.inputs[0].varType.getPrecision();
                const int                               scalarSize                                      = glu::getDataTypeScalarSize(type);
-               const bool                              transitSupportsSignedZero       = (m_shaderType != glu::SHADERTYPE_FRAGMENT); // executor cannot reliably transit negative zero to fragment stage
-               const bool                              signedZero                                      = supportsSignedZero(precision) && transitSupportsSignedZero;
+               const bool                              signedZero                                      = false;
 
                const int                               mantissaBits                            = getMinMantissaBits(precision);
                const deUint32                  maxUlpDiff                                      = getMaxUlpDiffFromBits(mantissaBits);