gdb/ChangeLog:

2006-01-18  Jim Blandy  <jimb@redhat.com>

	* configure.ac: Add -Wno-pointer-sign to list of build warnings.
	* configure: Regenerated.

gdb/doc/ChangeLog:
2006-01-18  Jim Blandy  <jimb@redhat.com>

	* gdbint.texinfo (Coding): Add entry for -Wno-pointer-sign to list
	of warning flags.
This commit is contained in:
Jim Blandy 2006-01-20 21:58:16 +00:00
parent b2a74f99b6
commit 7be93b9eea
5 changed files with 21 additions and 2 deletions

View File

@ -1,3 +1,8 @@
2006-01-20 Jim Blandy <jimb@redhat.com>
* configure.ac: Add -Wno-pointer-sign to list of build warnings.
* configure: Regenerated.
2006-01-20 Daniel Jacobowitz <dan@codesourcery.com>
* MAINTAINERS: Overhaul.

2
gdb/configure vendored
View File

@ -20105,7 +20105,7 @@ fi;
# gdb/doc/gdbint.texinfo.
build_warnings="-Wimplicit -Wreturn-type -Wcomment -Wtrigraphs \
-Wformat -Wparentheses -Wpointer-arith -Wformat-nonliteral \
-Wunused-label -Wunused-function"
-Wunused-label -Wunused-function -Wno-pointer-sign"
# GCC supports -Wuninitialized only with -O or -On, n != 0.
if test x${CFLAGS+set} = xset; then

View File

@ -1115,7 +1115,7 @@ AC_SUBST(TARGET_SYSTEM_ROOT_DEFINE)
# gdb/doc/gdbint.texinfo.
build_warnings="-Wimplicit -Wreturn-type -Wcomment -Wtrigraphs \
-Wformat -Wparentheses -Wpointer-arith -Wformat-nonliteral \
-Wunused-label -Wunused-function"
-Wunused-label -Wunused-function -Wno-pointer-sign"
# GCC supports -Wuninitialized only with -O or -On, n != 0.
if test x${CFLAGS+set} = xset; then

View File

@ -1,3 +1,8 @@
2006-01-18 Jim Blandy <jimb@redhat.com>
* gdbint.texinfo (Coding): Add entry for -Wno-pointer-sign to list
of warning flags.
2006-01-13 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Sequences): Improve menu annotations.

View File

@ -5016,6 +5016,15 @@ switch (sched)
@end smallexample
@item -Wunused-function
@item -Wno-pointer-sign
In version 4.0, GCC began warning about pointer argument passing or
assignment even when the source and destination differed only in
signedness. However, most @value{GDBN} code doesn't distinguish
carefully between @code{char} and @code{unsigned char}. In early 2006
the @value{GDBN} developers decided correcting these warnings wasn't
worth the time it would take.
@end table
@emph{Pragmatics: Due to the way that @value{GDBN} is implemented most