public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51412] New: [c++0x] Broken diagnostic with invalid lambda expressions
Date: Sun, 04 Dec 2011 21:52:00 -0000 [thread overview]
Message-ID: <bug-51412-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51412
Bug #: 51412
Summary: [c++0x] Broken diagnostic with invalid lambda
expressions
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: reichelt@gcc.gnu.org
A broken diagnostic is generated for the following invalid code snippet since
GCC 4.5.0:
==========================
void foo(int);
template<int> void bar()
{
foo([]{}...);
}
==========================
bug.cc: In function 'void bar()':
bug.cc:5:11: error: expansion pattern '#'lambda_expr' not supported by
dump_expr#<expression error>' contains no argument packs
A slightly modified testcase results in a similar diagnostic:
==========================
void foo(int);
template<int> void bar()
{
foo([]{}=0 ...);
}
==========================
bug.cc: In function 'void bar()':
bug.cc:5:14: error: expansion pattern '(#'lambda_expr' not supported by
pp_c_expression#)=0' contains no argument packs
next reply other threads:[~2011-12-04 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 21:52 reichelt at gcc dot gnu.org [this message]
2012-08-24 12:02 ` [Bug c++/51412] " redi at gcc dot gnu.org
2012-10-05 17:14 ` paolo.carlini at oracle dot com
2013-03-08 22:37 ` paolo at gcc dot gnu.org
2013-03-08 22:38 ` paolo.carlini at oracle dot com
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=bug-51412-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).