From f0183775d1575a4537bed8c10e9c757ffa66fe03 Mon Sep 17 00:00:00 2001 From: Olivier Goffart Date: Thu, 1 Oct 2009 10:43:09 +0200 Subject: Fix the compilerwarning test on GCC Don't issue this warning: comparing floating point with == or != is unsafe There is many of them and the Qt code is correct (it has to be fast comparison to know if fast code path must be taken) Reviewed-by: Jeremy --- tests/auto/compilerwarnings/tst_compilerwarnings.cpp | 1 - 1 file changed, 1 deletion(-) diff --git a/tests/auto/compilerwarnings/tst_compilerwarnings.cpp b/tests/auto/compilerwarnings/tst_compilerwarnings.cpp index 907aade..0be5cb0 100644 --- a/tests/auto/compilerwarnings/tst_compilerwarnings.cpp +++ b/tests/auto/compilerwarnings/tst_compilerwarnings.cpp @@ -179,7 +179,6 @@ void tst_CompilerWarnings::warnings() << "-Wno-long-long" << "-Wshadow" << "-Wpacked" << "-Wunreachable-code" << "-Wundef" << "-Wchar-subscripts" << "-Wformat-nonliteral" << "-Wformat-security" << "-Wcast-align" - << "-Wfloat-equal" << "-o" << tmpFile << tmpSourceFile; #elif defined(Q_CC_XLC) -- cgit v0.12