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++/48884] decltype's operand doesn't consider friend declaration Date: Tue, 24 May 2011 20:44:00 -0000 [thread overview] Message-ID: <bug-48884-4-uKcWbGh7ND@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48884-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48884 --- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> 2011-05-24 20:26:51 UTC --- Author: jason Date: Tue May 24 20:26:47 2011 New Revision: 174139 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174139 Log: PR c++/48884 * class.c (pushclass): Accept NULL argument. (popclass): Deal with popping null class. * pt.c (push_access_scope, pop_access_scope): Use them rather than push_to_top_level/pop_from_top_level. (push_deduction_access_scope, pop_defarg_context): New. (fn_type_unification): Use them. * name-lookup.c (lookup_name_real_1): Check current_class_type. Added: trunk/gcc/testsuite/g++.dg/template/access21.C trunk/gcc/testsuite/g++.dg/template/access22.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/class.c trunk/gcc/cp/name-lookup.c trunk/gcc/cp/pt.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-05-24 20:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-05 12:03 [Bug c++/48884] New: " boostcpp at gmail dot com 2011-05-05 12:40 ` [Bug c++/48884] " redi at gcc dot gnu.org 2011-05-23 19:47 ` jason at gcc dot gnu.org 2011-05-24 20:44 ` jason at gcc dot gnu.org [this message] 2011-05-25 1:36 ` jason at gcc dot gnu.org 2011-05-25 1:45 ` 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-48884-4-uKcWbGh7ND@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).