From: Tom Tromey <tromey@redhat.com>
To: Goncalo Gomes <goncalo@promisc.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Refactor tdep-i386.c to fix all -Wshadow warnings
Date: Mon, 06 Aug 2012 14:23:00 -0000 [thread overview]
Message-ID: <877gtckskw.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADF=+bYpAVcM2OsyGypeGjo2uV3_-mu6YphQgYrwUHY+wMOiaQ@mail.gmail.com> (Goncalo Gomes's message of "Sun, 5 Aug 2012 23:24:04 +0100")
>>>>> "Goncalo" == Goncalo Gomes <goncalo@promisc.org> writes:
Goncalo> The attached patch fixes all warnings in tdep-i386.c resulting from
Goncalo> enabling shadow warnings in gcc. As this is my first contribution to
Goncalo> GDB, I decided to keep it short to a single file to obtain feedback.
Just a friendly word of warning -- this is arguably the worst project to
pick of all the things on the project page (though unfortunately there
is more than one stinker on there). It's been attempted a couple of
times, had always lead to a lot of contention, etc.
That doesn't mean it can't be done, just that you ought to expect it to
be a pain.
Last time this came up, I think the conclusion was that we'd prefer it
if we could get warnings only for some kinds of shadowing, but not all
kinds. There was a sense that warnings for shadowing of 'index' was not
very useful. I remember some discussion of checking for a GCC change in
gdb's configure, but I don't remember the details any more. They're in
the archives.
Tom
next prev parent reply other threads:[~2012-08-06 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 22:24 Goncalo Gomes
2012-08-06 10:46 ` Sergio Durigan Junior
2012-08-06 13:34 ` Goncalo Gomes
2012-08-06 14:23 ` Tom Tromey [this message]
2012-08-06 17:18 ` Goncalo Gomes
2012-08-06 19:40 ` Sergio Durigan Junior
2012-08-09 9:21 ` Mark Kettenis
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=877gtckskw.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=goncalo@promisc.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