From: Paolo Carlini <paolo.carlini@oracle.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: RFA (libstdc++): C++/v3 PATCH for c++/24163 (lookup in dependent bases) and c++/29131
Date: Tue, 24 May 2011 11:50:00 -0000 [thread overview]
Message-ID: <4DDB8BA5.60507@oracle.com> (raw)
In-Reply-To: <4DDB2D1F.1010305@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
On 05/24/2011 05:59 AM, Jason Merrill wrote:
> It occurred to me today that I could use current_class_name rather
> than TYPE_IDENTIFIER (current_class_type).
Thus I suppose the below is also ok and obvious? To be safe, I'm testing
it on x86_64-linux.
Paolo.
//////////////////////
[-- Attachment #2: CL --]
[-- Type: text/plain, Size: 107 bytes --]
2011-05-24 Paolo Carlini <paolo.carlini@oracle.com>
* decl.c (grokdeclarator): Use current_class_name.
[-- Attachment #3: patchlet --]
[-- Type: text/plain, Size: 556 bytes --]
Index: decl.c
===================================================================
--- decl.c (revision 174105)
+++ decl.c (working copy)
@@ -9910,7 +9910,7 @@ grokdeclarator (const cp_declarator *declarator,
instantiation made the field's type be incomplete. */
if (current_class_type
&& TYPE_NAME (current_class_type)
- && IDENTIFIER_TEMPLATE (TYPE_IDENTIFIER (current_class_type))
+ && IDENTIFIER_TEMPLATE (current_class_name)
&& declspecs->type
&& declspecs->type == type)
error (" in instantiation of template %qT",
next prev parent reply other threads:[~2011-05-24 10:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 17:09 Jason Merrill
2011-05-20 18:26 ` Paolo Carlini
2011-05-20 19:46 ` Gabriel Dos Reis
2011-05-20 20:39 ` Jason Merrill
2011-05-20 21:56 ` Gabriel Dos Reis
2011-05-21 0:32 ` Joe Buck
2011-05-21 3:01 ` Christopher Jefferson
2011-05-21 3:44 ` Jason Merrill
2011-05-24 9:41 ` Jason Merrill
2011-05-24 11:50 ` Paolo Carlini [this message]
2011-05-24 18:51 ` Jason Merrill
2011-05-27 10:30 ` Jonathan Wakely
2011-05-27 12:26 ` Paolo Carlini
2011-05-27 12:34 ` Paolo Carlini
2011-05-28 1:08 ` Jonathan Wakely
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=4DDB8BA5.60507@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).