From: Michael Snyder <msnyder@vmware.com>
To: gdb@sourceware.org
Subject: A strange gcc behavior, and an argument against -Wno-unused
Date: Sat, 10 Oct 2009 00:48:00 -0000 [thread overview]
Message-ID: <4ACFD8B7.4090902@vmware.com> (raw)
Hey all,
We have "-Wno-unused" in our Makefile.in, as a result of which
we have accumulated a huge pool of unused variables, which
probably get optimized away and so don't hurt anything, but
which clutter up the code.
I was playing around with the idea of cleaning them up, and
so I removed the "-Wno-unused" from the makefile.
But the first thing that happened was that my compile failed
with the following warning (which of course was treated as an
error, because we also have -Werror):
i386-tdep.c:4149: warning: statement with no effect
Now here's the line in question, from i386_process_record:
ir.rm != ir.rex_b;
From context and other examples, I'm pretty sure that this
is a typo, and was meant to read "|=", not "!=". No sweat,
I'll fix it, or submit it for review anyway.
BUT! The fact that this escaped being detected by the compiler
bothers me a lot! I don't know whether to think of it as a
compiler bug, or to reason "well, we said "don't warn us about
things that are unused, and this is basically an unused
statement".
So, for discussion, should we remove -Wno-unused?
Michael
next reply other threads:[~2009-10-10 0:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 0:48 Michael Snyder [this message]
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
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=4ACFD8B7.4090902@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
/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