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++/52374] [C++11] Fails to transform id-expression into dependent base member access in lambda expression Date: Sun, 17 Mar 2013 02:42:00 -0000 [thread overview] Message-ID: <bug-52374-4-h5MSbrr2ui@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52374-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52374 --- Comment #1 from Jason Merrill <jason at gcc dot gnu.org> 2013-03-17 02:39:18 UTC --- Author: jason Date: Sun Mar 17 02:39:04 2013 New Revision: 196743 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196743 Log: PR c++/52374 * pt.c (tsubst_qualified_id): Use current_nonlambda_class_type. Added: trunk/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-this13.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/pt.c
next prev parent reply other threads:[~2013-03-17 2:40 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-24 16:50 [Bug c++/52374] New: " ai.azuma at gmail dot com 2012-02-24 17:20 ` [Bug c++/52374] " redi at gcc dot gnu.org 2013-03-13 2:53 ` jason at gcc dot gnu.org 2013-03-17 2:42 ` jason at gcc dot gnu.org [this message] 2013-03-23 19:24 ` jason at gcc dot gnu.org
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-52374-4-h5MSbrr2ui@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).