From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, dave.korn.cygwin@googlemail.com, msnyder@vmware.com
Subject: Re: A strange gcc behavior, and an argument against -Wno-unused
Date: Tue, 13 Oct 2009 14:09:00 -0000 [thread overview]
Message-ID: <200910131509.40897.pedro@codesourcery.com> (raw)
In-Reply-To: <83d44vjaiy.fsf@gnu.org>
Since Michael has committed his patch meanwhile, in the
interest of moving a bit forward, how 'bout we give this a
try, then? No new warnings caught on an
'x86_64-linux --enable-targets=all' at -O2 build.
--
Pedro Alves
2009-10-13 Pedro Alves <pedro@codesourcery.com>
gdb/
* configure.ac (build_warnings): Add -Wunused-value.
* configure: Regenerate.
---
gdb/configure | 2 +-
gdb/configure.ac | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Index: src/gdb/configure.ac
===================================================================
--- src.orig/gdb/configure.ac 2009-10-11 15:53:33.000000000 +0100
+++ src/gdb/configure.ac 2009-10-11 15:54:10.000000000 +0100
@@ -1542,7 +1542,7 @@ fi
# gdb/doc/gdbint.texinfo.
build_warnings="-Wall -Wdeclaration-after-statement -Wpointer-arith \
-Wformat-nonliteral -Wno-pointer-sign \
--Wno-unused -Wno-switch -Wno-char-subscripts"
+-Wno-unused -Wunused-value -Wno-switch -Wno-char-subscripts"
# Enable -Wno-format by default when using gcc on mingw since many
# GCC versions complain about %I64.
Index: src/gdb/configure
===================================================================
--- src.orig/gdb/configure 2009-10-11 15:53:33.000000000 +0100
+++ src/gdb/configure 2009-10-11 15:54:10.000000000 +0100
@@ -13117,7 +13117,7 @@ fi
# gdb/doc/gdbint.texinfo.
build_warnings="-Wall -Wdeclaration-after-statement -Wpointer-arith \
-Wformat-nonliteral -Wno-pointer-sign \
--Wno-unused -Wno-switch -Wno-char-subscripts"
+-Wno-unused -Wunused-value -Wno-switch -Wno-char-subscripts"
# Enable -Wno-format by default when using gcc on mingw since many
# GCC versions complain about %I64.
next prev parent reply other threads:[~2009-10-13 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 0:48 Michael Snyder
2009-10-10 2:24 ` Dave Korn
2009-10-10 16:45 ` Pedro Alves
2009-10-10 18:08 ` Eli Zaretskii
2009-10-10 18:24 ` Pedro Alves
2009-10-10 18:25 ` Tom Tromey
2009-10-10 18:37 ` Eli Zaretskii
2009-10-10 18:50 ` Pedro Alves
2009-10-10 19:46 ` Eli Zaretskii
2009-10-13 14:09 ` Pedro Alves [this message]
2009-10-13 15:33 ` Pierre Muller
2009-10-13 16:42 ` Tom Tromey
2009-10-13 15:48 ` Tom Tromey
2009-10-14 19:45 ` Pedro Alves
2009-10-10 18:30 ` Tom Tromey
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=200910131509.40897.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=tromey@redhat.com \
/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