public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53783] [4.8 Regression] lambda in lambda in template function rejected Date: Mon, 10 Sep 2012 23:51:00 -0000 [thread overview] Message-ID: <bug-53783-4-9Ko5wK0Q8f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53783-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53783 --- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> 2012-09-10 23:51:41 UTC --- Author: jason Date: Mon Sep 10 23:51:34 2012 New Revision: 191164 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=191164 Log: PR c++/54538 PR c++/53783 * pt.c (tsubst_copy_and_build) [LAMBDA_EXPR]: Go back to using RECUR for LAMBDA_EXPR_EXTRA_SCOPE except for function scope. Added: trunk/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-mangle4.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/pt.c trunk/gcc/testsuite/ChangeLog
prev parent reply other threads:[~2012-09-10 23:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-26 22:53 [Bug c++/53783] New: " lunow at math dot hu-berlin.de 2012-06-27 9:31 ` [Bug c++/53783] " rguenth at gcc dot gnu.org 2012-07-03 5:03 ` jason at gcc dot gnu.org 2012-07-03 5:06 ` jason at gcc dot gnu.org 2012-09-10 23:51 ` jason at gcc dot gnu.org [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=bug-53783-4-9Ko5wK0Q8f@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: linkBe 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).