From: Paolo Carlini <paolo.carlini@oracle.com>
To: Jason Merrill <jason@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch / RFC] PR 50870
Date: Fri, 28 Oct 2011 02:00:00 -0000 [thread overview]
Message-ID: <4EA9F5BB.7010408@oracle.com> (raw)
In-Reply-To: <4EA9F0D3.4040800@oracle.com>
.. maybe one final piece of information for today.
I'm trying to figure out where the very different args argument is
coming from.
Both in 4.5 and in mainline we have the same final chain of
tusbst_copy_build, preceded by tsubst_copy_and_build, tusbst_expr,
tsubt, tsubst_template_arg, the args argument remains the same all the way.
Earlier than that things are different: in mainline the same args, as
arglist, comes from fixup_template_parm, and earlier we have
fixup_template_parms which creates the arglist itself, even earlier the
parser.
In 4.5 before tsubst_template_arg we have coerce_template_parms, which
changes its args argument to the final value, and before that
lookup_template_class, finish_template_type, the parser.
Paolo.
next prev parent reply other threads:[~2011-10-28 0:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 15:28 Paolo Carlini
2011-10-26 16:25 ` Jason Merrill
2011-10-26 17:12 ` Paolo Carlini
2011-10-26 18:15 ` Jason Merrill
2011-10-26 22:54 ` Paolo Carlini
2011-10-26 23:23 ` Paolo Carlini
2011-10-27 0:00 ` Jason Merrill
2011-10-27 0:01 ` Paolo Carlini
2011-10-27 0:02 ` Paolo Carlini
2011-10-27 7:38 ` Jason Merrill
2011-10-27 12:34 ` Paolo Carlini
2011-10-27 13:16 ` Jason Merrill
2011-10-27 13:19 ` Paolo Carlini
2011-10-27 13:20 ` Jason Merrill
2011-10-27 14:56 ` Paolo Carlini
2011-10-27 23:29 ` Paolo Carlini
2011-10-28 1:44 ` Paolo Carlini
2011-10-28 2:00 ` Paolo Carlini [this message]
2011-10-28 16:59 ` Jason Merrill
2011-10-28 17:00 ` Paolo Carlini
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=4EA9F5BB.7010408@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).