Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: goncalo@promisc.org, gdb-patches@sourceware.org
Subject: Re: Refactor tdep-i386.c to fix all -Wshadow warnings
Date: Thu, 09 Aug 2012 09:21:00 -0000	[thread overview]
Message-ID: <201208090920.q799Kh8Q021002@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <877gtckskw.fsf@fleche.redhat.com> (message from Tom Tromey on	Mon, 06 Aug 2012 08:23:11 -0600)

> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 06 Aug 2012 08:23:11 -0600
> 
> >>>>> "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.

Right.  In particular the case where a local variable "shadows" a
global function.  Until GCC stops warning about those cases I think we
should leave the -Wshadow issue alone.


      parent reply	other threads:[~2012-08-09  9:21 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
2012-08-06 17:18   ` Goncalo Gomes
2012-08-06 19:40   ` Sergio Durigan Junior
2012-08-09  9:21   ` Mark Kettenis [this message]

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=201208090920.q799Kh8Q021002@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=goncalo@promisc.org \
    --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