From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Dodji Seketeli <dodji@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH] PR c++/55663 - constexpr function templ instantiation considered non-const as alias templ arg
Date: Thu, 10 Jan 2013 16:11:00 -0000 [thread overview]
Message-ID: <CAAiZkiApGZ3_ZU+b6ARhko=4PPsgc86sC_Xqg9GbfDw=PZHLLg@mail.gmail.com> (raw)
In-Reply-To: <87k3rlrrkw.fsf@redhat.com>
On Thu, Jan 10, 2013 at 9:22 AM, Dodji Seketeli <dodji@redhat.com> wrote:
> But during the instantiation of the *members* of test<int>, we try to
> instantiate Alias<the_truth<int>>, without coercing (and thus without
> folding) the argument {the_truth<int>}. We do this using
> instantiate_alias_template, called from tsubst.
>
> The patch below makes sure instantiate_alias_template coerces the
> arguments it uses to instantiate the alias template, like what I
> understood you are suggesting. I have tested it without boostrap and a
> full boostrap is currently running.
Hmm, is it necessary to coerce all levels as opposed to just the
innermost arguments?
-- Gaby
next prev parent reply other threads:[~2013-01-10 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 13:58 Dodji Seketeli
2013-01-08 16:44 ` Gabriel Dos Reis
2013-01-09 15:31 ` Dodji Seketeli
2013-01-09 16:14 ` Gabriel Dos Reis
2013-01-10 15:22 ` Dodji Seketeli
2013-01-10 16:02 ` Gabriel Dos Reis
2013-01-11 10:41 ` Dodji Seketeli
2013-01-11 10:47 ` Jakub Jelinek
2013-01-11 11:31 ` Dodji Seketeli
2013-01-10 16:11 ` Gabriel Dos Reis [this message]
2013-01-10 17:01 ` Jason Merrill
2013-01-11 10:38 ` Dodji Seketeli
2013-01-11 14:53 ` Jason Merrill
2013-01-11 16:33 ` Dodji Seketeli
2013-01-14 14:09 ` Jason Merrill
2013-01-08 19:53 ` Jason Merrill
2013-01-09 15:03 ` Dodji Seketeli
2013-01-09 16:17 ` Jason Merrill
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='CAAiZkiApGZ3_ZU+b6ARhko=4PPsgc86sC_Xqg9GbfDw=PZHLLg@mail.gmail.com' \
--to=gdr@integrable-solutions.net \
--cc=dodji@redhat.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).