From: Joel Brobecker <brobecker@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [RFA] statement before variable declaration in cp_parser_initializer_list.
Date: Thu, 03 Jan 2013 12:31:00 -0000 [thread overview]
Message-ID: <1357216224-513-1-git-send-email-brobecker@adacore.com> (raw)
Hello,
I happened to notice a warning while compiling GCC, and it seemed
like an easy fix...
gcc/cp/ChangeLog:
* parser.c (cp_parser_initializer_list): Move declaration
of variable non_const to start of lexical block.
Tested against x86_64-linux, no regression.
OK to commit? (obvious?)
Thanks,
--
Joel
---
gcc/cp/parser.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/gcc/cp/parser.c b/gcc/cp/parser.c
index 3dc2ec6..61d93f8 100644
--- a/gcc/cp/parser.c
+++ b/gcc/cp/parser.c
@@ -17932,9 +17932,10 @@ cp_parser_initializer_list (cp_parser* parser, bool* non_constant_p)
&& cp_lexer_next_token_is (parser->lexer, CPP_OPEN_SQUARE))
{
/* In C++11, [ could start a lambda-introducer. */
+ bool non_const = false;
+
cp_parser_parse_tentatively (parser);
cp_lexer_consume_token (parser->lexer);
- bool non_const = false;
designator = cp_parser_constant_expression (parser, true, &non_const);
cp_parser_require (parser, CPP_CLOSE_SQUARE, RT_CLOSE_SQUARE);
cp_parser_require (parser, CPP_EQ, RT_EQ);
--
1.7.0.4
next reply other threads:[~2013-01-03 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 12:31 Joel Brobecker [this message]
2013-01-03 12:33 ` Richard Biener
2013-01-03 12:37 ` Joel Brobecker
2013-01-03 12:57 ` Richard Biener
2013-01-08 11:37 ` Joel Brobecker
2013-01-08 11:51 ` Richard Biener
2013-01-08 12:36 ` Joel Brobecker
2013-01-03 12:55 ` Eric Botcazou
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=1357216224-513-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.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).