From: Jason Merrill <jason@redhat.com>
To: 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 09:41:00 -0000 [thread overview]
Message-ID: <4DDB2D1F.1010305@redhat.com> (raw)
In-Reply-To: <4DD69790.8070101@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 159 bytes --]
It occurred to me today that I could use current_class_name rather than
TYPE_IDENTIFIER (current_class_type).
Tested x86_64-pc-linux-gnu, applied to trunk.
[-- Attachment #2: 24163-tweak.patch --]
[-- Type: text/x-patch, Size: 609 bytes --]
commit d40ebc9ef2be8ab9b4d71410d9797442b2c16d9a
Author: Jason Merrill <jason@redhat.com>
Date: Mon May 23 15:23:42 2011 -0400
* pt.c (tsubst_copy_and_build): Use current_class_name.
diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
index 4299733..dbff91e 100644
--- a/gcc/cp/pt.c
+++ b/gcc/cp/pt.c
@@ -13017,8 +13017,7 @@ tsubst_copy_and_build (tree t,
else
inform (EXPR_LOC_OR_HERE (t),
"use %<%T::%D%> instead",
- TYPE_IDENTIFIER (current_class_type),
- function);
+ current_class_name, function);
}
else
inform (0, "%q+D declared here, later in the "
next prev parent reply other threads:[~2011-05-24 3:59 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 [this message]
2011-05-24 11:50 ` Paolo Carlini
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=4DDB2D1F.1010305@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@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).