From cc0a53dc9699268643967ee575d8236b77bdb1a5 Mon Sep 17 00:00:00 2001
From: Vadim Zeitlin <vadim@wxwidgets.org>
Date: Sat, 19 Sep 2015 03:28:50 +0200
Subject: [PATCH] Don't use -fno-strict-aliasing for optimized build

There doesn't seem to be any need for it, the library compiles fine without it
and the few warnings generated with -Wstrict-aliasing=2 are harmless (i.e. the
strict aliasing rule is not really broken).
---
 configure    | 2 +-
 configure.in | 5 +----
 2 files changed, 2 insertions(+), 5 deletions(-)

diff --git a/configure b/configure
index 209198cb7e..b5231f48a2 100755
--- a/configure
+++ b/configure
@@ -32915,7 +32915,7 @@ else
         fi
     else
         if test "$GCC" = yes ; then
-                                                OPTIMISE_CFLAGS="-O2 -fno-strict-aliasing"
+            OPTIMISE_CFLAGS="-O2"
         else
             OPTIMISE_CFLAGS="-O"
         fi
diff --git a/configure.in b/configure.in
index 8b5a31eebe..70df888ae0 100644
--- a/configure.in
+++ b/configure.in
@@ -5101,10 +5101,7 @@ else
         fi
     else
         if test "$GCC" = yes ; then
-            dnl Switch on optimisation but keep strict-aliasing off for
-            dnl now (see -fstrict-aliasing in the gcc manual). When it is
-            dnl switched back on consider using -Wstrict-aliasing=2.
-            OPTIMISE_CFLAGS="-O2 -fno-strict-aliasing"
+            OPTIMISE_CFLAGS="-O2"
         else
             OPTIMISE_CFLAGS="-O"
         fi