From: Jim Meyering <jim@meyering.net>
To: gcc-patches@gcc.gnu.org, dnovillo@google.com
Subject: adding -Wshadow-local and -Wshadow-compatible-local ?
Date: Fri, 11 Dec 2015 23:42:00 -0000 [thread overview]
Message-ID: <CA+8g5KEH=a3OjwP23rtQ6TPqdJejC9WNqCbK9m+9wdmt_ckEDw@mail.gmail.com> (raw)
Hi Diego,
I noticed this patch that adds support for improved -Wshadow-related options:
[google] Add two new -Wshadow warnings (issue4452058)
https://gcc.gnu.org/ml/gcc-patches/2011-04/msg02317.html
https://codereview.appspot.com/4452058/
Here are the proposed descriptions:
-Wshadow-local which warns if a local variable shadows another local
variable or parameter,
-Wshadow-compatible-local which warns if a local variable shadows another
local variable or parameter whose type is compatible with that of the
shadowing variable.
Yet, I see no further discussion of them, other than Jason's review feedback.
Was this change deemed unsuitable for upstream gcc?
Thanks,
Jim
next reply other threads:[~2015-12-11 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 23:42 Jim Meyering [this message]
2015-12-14 14:46 ` Diego Novillo
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='CA+8g5KEH=a3OjwP23rtQ6TPqdJejC9WNqCbK9m+9wdmt_ckEDw@mail.gmail.com' \
--to=jim@meyering.net \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).