From: Tom Tromey <tromey@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb@sourceware.org
Subject: Re: Switch -Wunused-variable on?
Date: Mon, 23 Apr 2012 14:30:00 -0000 [thread overview]
Message-ID: <87sjfufrlr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3bomjy0ov.fsf@redhat.com> (Sergio Durigan Junior's message of "Sun, 22 Apr 2012 17:24:32 -0300")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
Jan> IIRC the counterargument for -Wunused-variable was that GDB
Jan> contains various #if-compiled code where is a nightmare to get the
Jan> code right with matching #if-clauses also for the variables being
Jan> used by various #if-compiled code chunks. I could not find that
Jan> mail now in the time I gave to it.
Sergio> Yes, this is a counter-argument, and I was also thinking about it. I
Sergio> don't know how people prefer to deal with this issue, but something
Sergio> like:
Sergio> #define USED_VAR(var) ((void) var)
Sergio> Would be OK?
That sort of thing obscures whether the variable later dies.
I'd say that the best approach would be to make the declarations
conditional in the same way that the uses are.
If there are a lot of problem cases with this approach, or if it makes
the code too ugly, then maybe it would be better just not to use this
flag.
Tom
next prev parent reply other threads:[~2012-04-23 14:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 8:06 Sergio Durigan Junior
2012-04-22 8:23 ` Jan Kratochvil
2012-04-22 20:25 ` Sergio Durigan Junior
2012-04-22 22:25 ` Jeffrey Walton
2012-04-23 8:55 ` Jan Kratochvil
2012-04-23 14:30 ` Tom Tromey [this message]
2012-04-23 15:49 ` Sergio Durigan Junior
2012-04-23 18:02 ` Pedro Alves
2012-04-23 18:39 ` Michael Eager
2012-04-24 22:11 ` Maciej W. Rozycki
2012-04-25 7:51 ` Andreas Schwab
2012-04-25 15:57 ` Maciej W. Rozycki
2012-04-25 16:50 ` Andreas Schwab
2012-04-25 17:22 ` Maciej W. Rozycki
2012-04-25 18:13 ` Andreas Schwab
2012-04-25 18:20 ` Sterling Augustine
2012-04-25 18:52 ` Maciej W. Rozycki
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=87sjfufrlr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=sergiodj@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