Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Subject: Re: build gdbserver with -Werror by default
Date: Fri, 27 Aug 2010 10:29:00 -0000	[thread overview]
Message-ID: <201008271129.08333.pedro@codesourcery.com> (raw)
In-Reply-To: <001e01cb45c5$a6b53b40$f41fb1c0$@muller@ics-cnrs.unistra.fr>

On Friday 27 August 2010 09:55:11, Pierre Muller wrote:
>   Hi Pedro,
> 
>   Cygwin 1.7 fails on gdbserver:
> gcc -c -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -
> Werror -gstabs+ -O0    -I. -I../../../src/gdb/gdbserver -I../../../src/gdb/gdbse
> rver/../common -I../../../src/gdb/gdbserver/../regformats -I../../../src/gdb/gdb
> server/../../include ../../../src/gdb/gdbserver/tracepoint.c
> cc1: warnings being treated as errors
> ../../../src/gdb/gdbserver/tracepoint.c: In function `add_tracepoint_action':
> ../../../src/gdb/gdbserver/tracepoint.c:1870: error: array subscript has type `c
> har'
> make[3]: *** [tracepoint.o] Error 1
> 
>   isxdigit argument type is int, not char according to man page...
> Adding an explicit typecast to int at that line
> allows to go to compilation of win32-low.c, 

and it'd fail elsewhere if it kept going, most probably.  GDB has
a bunch of suspicious code like this as well (e.g., in remote.c), so it
ended up with -Wno-char-subscripts.  I didn't bring that warning over to
gdbserver, as I didn't see any warning when building for linux and
mingw32, so I thought it was unnecessary (it is probably gcc version
dependent whether that's part of -Wall).  Since this is certainly
not a new warning (it's the fact that it causes an error that it's new)
I've now added -Wno-char-subscripts to gdbserver as well...

> but there you
> end up with warnings about deprecated functions...
>   To fix that, you would need to use the same kind of macros
> as in gdb/windows-nat.c

Hmm, I have no clue about what deprecated warnings are these,
and what macros you're talking about.  Are these new warnings, or
it is just that they've been there before, but ignored?

-- 
Pedro Alves

2010-08-27  Pedro Alves  <pedro@codesourcery.com>

	* configure.ac (build_warnings): Add -Wno-char-subscripts.
	* configure: Regenerate.

---
 gdb/gdbserver/configure    |    2 +-
 gdb/gdbserver/configure.ac |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Index: src/gdb/gdbserver/configure.ac
===================================================================
--- src.orig/gdb/gdbserver/configure.ac	2010-08-26 19:32:03.000000000 +0100
+++ src/gdb/gdbserver/configure.ac	2010-08-27 11:02:56.000000000 +0100
@@ -112,7 +112,7 @@ if test "${ERROR_ON_WARNING}" = yes ; th
 fi
 
 build_warnings="-Wall -Wdeclaration-after-statement -Wpointer-arith \
--Wformat-nonliteral "
+-Wformat-nonliteral -Wno-char-subscripts"
 
 WARN_CFLAGS=""
 if test "x$GCC" = xyes
Index: src/gdb/gdbserver/configure
===================================================================
--- src.orig/gdb/gdbserver/configure	2010-08-26 19:32:03.000000000 +0100
+++ src/gdb/gdbserver/configure	2010-08-27 11:03:45.000000000 +0100
@@ -3944,7 +3944,7 @@ if test "${ERROR_ON_WARNING}" = yes ; th
 fi
 
 build_warnings="-Wall -Wdeclaration-after-statement -Wpointer-arith \
--Wformat-nonliteral "
+-Wformat-nonliteral -Wno-char-subscripts"
 
 WARN_CFLAGS=""
 if test "x$GCC" = xyes


  reply	other threads:[~2010-08-27 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 18:18 Pedro Alves
2010-08-27  8:57 ` Pierre Muller
2010-08-27 10:29   ` Pedro Alves [this message]
2010-08-27 14:50     ` Daniel Jacobowitz
2010-08-27 14:54       ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008271129.08333.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox