From fa389cd2a117370217ce213ea670ce9055bb0284 Mon Sep 17 00:00:00 2001 From: Matthew Barnes Date: Thu, 5 Aug 2010 08:44:22 -0400 Subject: Bug 626090 - Only set -fno-strict-aliasing for GCC --- configure.ac | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/configure.ac b/configure.ac index 9bc4ef8e93..857248367f 100644 --- a/configure.ac +++ b/configure.ac @@ -175,12 +175,6 @@ dnl -Wstrict-aliasing=2 dnl -DE_BOOK_DISABLE_DEPRECATED dnl -DE_CAL_DISABLE_DEPRECATED -dnl GCC 4.4 got more aggressive in its aliasing optimizations, changing -dnl behavior that -- according to the C99 standard -- is supposed to be -dnl undefined. We may still have aliasing abuses lying around that rely -dnl on GCC's previous "undefined" behavior, so disable strict-aliasing -dnl optimzation until we can find and fix all the abuses. -dnl XXX This really belongs in AM_CFLAGS. AM_CPPFLAGS="$WARNING_FLAGS -fno-strict-aliasing" AC_SUBST(AM_CPPFLAGS) @@ -223,6 +217,17 @@ AC_SUBST(PERL) AC_ARG_PROGRAM +dnl GCC 4.4 got more aggressive in its aliasing optimizations, changing +dnl behavior that -- according to the C99 standard -- is supposed to be +dnl undefined. We may still have aliasing abuses lying around that rely +dnl on GCC's previous "undefined" behavior, so disable strict-aliasing +dnl optimzation until we can find and fix all the abuses. +dnl (AC_PROG_CC must run first to set the GCC variable.) +dnl XXX This really belongs in AM_CFLAGS. +if test "x${GCC}" = "xyes"; then + CFLAGS="$CFLAGS -fno-strict-aliasing" +fi + dnl ****************************** dnl I18N stuff dnl ****************************** -- cgit v1.2.3