2013-05-15 Paul Eggert <eggert@cs.ucla.edu>
+ manywarnings: update for GCC 4.8.0
+ * m4/manywarnings.m4 (gl_MANYWARN_ALL_GCC):
+ Add -Waggressive-loop-optimizations, -Wreturn-local-addr, which
+ are new to GCC 4.8. Remove -Wformat=2, -Wmissing-format-attribute,
+ -Wmissing-noreturn, as they are duplicates of other warnings.
+ Remove -Wunreachable-code, as it is removed in GCC 4.8 and
+ was documented to be flaky in earlier versions of GCC.
+
+ spawn-tests, sys_socket-tests, sys_wait-tests: port to clang
+ * tests/test-spawn.c (main):
+ * tests/test-sys_socket.c (main):
+ * tests/test-sys_wait.c (main):
+ Don't have a switch value that isn't covered by a case.
+
+ getaddrinfo-tests: port --enable-gcc-warnings to clang
+ * tests/test-getaddrinfo.c (simple):
+ Avoid casts from looser to stricter-aligned pointers.
+
+ thread: port --enable-gcc-warnings to clang
+ * lib/glthread/thread.h [__clang__ && USE_POSIX_THREADS_WEAK]:
+ Include <signal.h>, to pacify a warning about pthread_sigmask.
+
+ stdio: use __REDIRECT for fwrite, fwrite_unlocked
+ * lib/stdio.in.h (fwrite):
+ When working around bug 11959, use __REDIRECT rather than '#define
+ fwrite(...) ... fwrite (...) ...'. This is a more-targeted way to
+ fix the -Wunused-value issue with clang, and it works with GCC too.
+ Problem with targeting reported by Eric Blake in
+ <http://lists.gnu.org/archive/html/bug-gnulib/2013-05/msg00067.html>.
+ (fwrite_unlocked): Treat like fwrite. I ran into this issue while
+ debugging the fwrite issue.
+
stdio: port --enable-gcc-warnings to clang
* lib/stdio.in.h (fwrite) [__clang__]: Ignore -Wunused-value entirely,
since the GCC workaround for fwrite does not pacify clang.
projects / gnulib.git / blobdiff