summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChad Versace <chad.versace@linux.intel.com>2012-08-09 12:59:22 -0700
committerChad Versace <chad.versace@linux.intel.com>2012-08-10 09:59:41 -0700
commit9f5a5d541d5c1ff2e440791ba8ff44d0233daeb4 (patch)
tree7bb8653759859cbcbc09dadc04cc9eb4d83aeced
parentf7af4beae5e25c060d4f2c53d55b0e87ee9bdaeb (diff)
mesa: Remove C++11 narrowing warnings
Add -Wno-narrowing to CXXFLAGS for gcc. It is safe to add this flag even for versions of gcc that don't recognize it. From the GCC Manual [1]: "[GCC] allows the use of new -Wno- options with old compilers". This removes warnings of the form warning: narrowing conversion of X from 'int' to 'float' inside { } is ill-formed in C++11 [-Wnarrowing] in ff_fragment_shader.cpp and gen6_blorp.cpp of the form. When building i965, I observed no other difference in the build output. [1] http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html Reviewed-by: Kenneth Graunke <kenneth@whitecape.org> Signed-off-by: Chad Versace <chad.versace@linux.intel.com>
-rw-r--r--configure.ac3
1 files changed, 3 insertions, 0 deletions
diff --git a/configure.ac b/configure.ac
index 89686b47fcf..fa4fd712717 100644
--- a/configure.ac
+++ b/configure.ac
@@ -228,6 +228,9 @@ if test "x$GXX" = xyes; then
# gcc's builtin memcmp is slower than glibc's
# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43052
CXXFLAGS="$CXXFLAGS -fno-builtin-memcmp"
+
+ # Silence C++11 warnings that we don't care about.
+ CXXFLAGS="$CXXFLAGS -Wno-narrowing"
fi
dnl even if the compiler appears to support it, using visibility attributes isn't