Revert "Try to suppress a compiler feature that goes wrong."
authorJoão Valverde <joao.valverde@tecnico.ulisboa.pt>
Thu, 7 Apr 2016 18:00:19 +0000 (19:00 +0100)
committerJoão Valverde <j@v6e.pt>
Thu, 7 Apr 2016 18:03:31 +0000 (18:03 +0000)
This reverts commit ec075789e31942008eb8ad7faf35b7012778dac8.

Change-Id: I6f84f01f2027f32d3727dd9d7d097d6d90e063c2
Reviewed-on: https://code.wireshark.org/review/14851
Reviewed-by: João Valverde <j@v6e.pt>
configure.ac

index 1dbe9fd6b90f0e737f867fa31ef61d8a9e0063b8..87ea6e46328d51149af5e45dda6b36f813d6ad50 100644 (file)
@@ -882,22 +882,6 @@ AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wno-long-long)
 AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wheader-guard)
 AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wunused-const-variable)
 #
-# Either the version of clang on the "clang code analysis" buildbot is
-# horribly broken, or the header files on that buildbot are horribly
-# broken, as the perfectly-legitimate statement
-#
-#      if( strcmp(argv[i],"--")==0 ) dashdash = 1;
-#
-# is getting stoopid "array index 3 is past the end of the array (which
-# contains 3 elements)" complaints from the compiler.
-#
-# The macro for strcmp() in glibc(?) really seems to give C compilers
-# conniptions; I think I've seen crap from GCC as well with that macro.
-#
-# So, alas, suppress the compile-time array bounds checks.
-#
-AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wnoarray-bounds)
-#
 # The following are C only, not C++
 #
 AC_WIRESHARK_COMPILER_FLAGS_CHECK(-Wc++-compat, C)