From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Cc: dave.korn.cygwin@googlemail.com, msnyder@vmware.com
Subject: Re: A strange gcc behavior, and an argument against -Wno-unused
Date: Sat, 10 Oct 2009 18:24:00 -0000 [thread overview]
Message-ID: <200910101924.12313.pedro@codesourcery.com> (raw)
In-Reply-To: <83iqenjf1f.fsf@gnu.org>
On Saturday 10 October 2009 19:10:36, Eli Zaretskii wrpte:
> What version of GCC introduced this switch?
If you're worried about breaking the build with older
gcc's, note that gdb/configure.ac filters out -W options
that gcc doesn't recognize.
if test "x${build_warnings}" != x -a "x$GCC" = xyes
then
AC_MSG_CHECKING(compiler warning flags)
# Separate out the -Werror flag as some files just cannot be
# compiled with it enabled.
for w in ${build_warnings}; do
case $w in
-Werr*) WERROR_CFLAGS=-Werror ;;
*) # Check that GCC accepts it
saved_CFLAGS="$CFLAGS"
CFLAGS="$CFLAGS $w"
AC_TRY_COMPILE([],[],WARN_CFLAGS="${WARN_CFLAGS} $w",)
CFLAGS="$saved_CFLAGS"
esac
done
AC_MSG_RESULT(${WARN_CFLAGS} ${WERROR_CFLAGS})
fi
That said, I don't know when the switch was introduced
in gcc.
--
Pedro Alves
next prev parent reply other threads:[~2009-10-10 18:24 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 [this message]
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
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=200910101924.12313.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 \
/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