Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
	Mike Frysinger <vapier@gentoo.org>,
	gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 22/348] Fix -Wsahdow warnings
Date: Wed, 23 Nov 2011 20:16:00 -0000	[thread overview]
Message-ID: <20111123201613.GO13809@adacore.com> (raw)
In-Reply-To: <CADPb22Sb-dESBNB0S+Y7936KkPaJofjXD6pbOvaFKDvcDUuDeA@mail.gmail.com>

> > Also, given the quantity, I'd suggest holding off until after 7.4 is branched.
> > [just a suggestion though]
> 
> Heh, OTOH ...
> It will make backporting fixes into the 7.4 branch harder if a lot go
> in right after it's branched.
> That suggests holding off until 7.4 is close to going out.
> 
> OTOOH, holding off too long will just make it harder for you to keep
> your patches up to date.
> But I wouldn't hold up 7.4 for these changes.
> 
> In the end I think the high order bit is not making it too difficult
> to backport fixes into the 7.4 branch.

I agree that the priority is to make merging easy.

I'm also starting to question the benefits vs cost of enabling
-Wshadow.  In particular, warnings that for us to change the name
of function parameters such as "block_found" or "index" make me feel
like this is going too far.

I think it's useful to review the warnings, because it did find some
real situation where we were shadowing another variable from an outer
scope. But I tend to disagree with a good portion of the warnings
I am seeing right now. Add the fact that the warnings also depend
on the host's system includes, and you might be as uncomfortable
as I am...

-- 
Joel


  reply	other threads:[~2011-11-23 20:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 13:07 Andrey Smirnov
2011-11-22 13:14 ` Eli Zaretskii
2011-11-22 13:34   ` Andrey Smirnov
2011-11-22 13:35     ` Marek Polacek
2011-11-22 14:04       ` Andrey Smirnov
2011-11-22 15:28         ` Mike Frysinger
2011-11-22 16:05           ` Joel Brobecker
2011-11-22 16:20             ` Mike Frysinger
2011-11-23 17:25               ` Doug Evans
2011-11-22 18:24             ` Tom Tromey
2011-11-23 16:46             ` Mark Kettenis
     [not found]               ` <CAHQ1cqFADK_pXv4JAW6ouvm_NPyM6dM+-FmVF0FojKi1rs98Wg@mail.gmail.com>
2011-11-24  3:23                 ` Andrey Smirnov
2011-11-23  5:29           ` Andrey Smirnov
2011-11-23 17:06             ` Tom Tromey
2011-11-24  3:18               ` Andrey Smirnov
2011-11-23 17:56             ` Doug Evans
2011-11-23 18:03               ` Doug Evans
2011-11-23 20:16                 ` Joel Brobecker [this message]
2011-11-24  4:33               ` Andrey Smirnov
2011-11-29 19:06                 ` Tom Tromey
2011-11-28 15:07         ` [PATCH 022/238] [misc.] bcache.c: -Wshadow fix Andrey Smirnov
2011-11-28 15:07           ` [PATCH 025/238] " Andrey Smirnov
2011-12-20 15:42             ` Tom Tromey
2011-11-28 15:07           ` [PATCH 026/238] " Andrey Smirnov
2011-12-20 15:43             ` Tom Tromey
2011-11-28 15:07           ` [PATCH 024/238] " Andrey Smirnov
2011-12-20 15:46             ` Tom Tromey
2011-12-20 15:42           ` [PATCH 022/238] " Tom Tromey
2011-12-20 16:13             ` Andrey Smirnov
2011-12-20 19:17               ` Tom Tromey
2011-12-20 19:31                 ` Andrey Smirnov
2011-12-20 21:06                   ` 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=20111123201613.GO13809@adacore.com \
    --to=brobecker@adacore.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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