From: Paolo Carlini <paolo.carlini@oracle.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: Re: [C++ Patch/RFC] PR 89900 ("[9 Regression] ICE: Segmentation fault (in check_instantiated_arg)")
Date: Fri, 12 Apr 2019 10:02:00 -0000 [thread overview]
Message-ID: <a2c97024-39d8-6212-06f3-819419d9bc2e@oracle.com> (raw)
In-Reply-To: <71f91c87-d690-89d8-4275-798214c86df4@oracle.com>
.. an additional observation. Over the last couple of days I wondered
if the amended testcase was really valid, given the non-terminal
parameter pack, beyond the evidence that all the compilers I have at
hand accept it. Note anyway, that we - and all the compilers - already
accept a version of the testcase without the explicit argument and
deduce the pack as empty:
template<typename ...XE> void
fk (XE..., int);
void
w9 (void)
{
 fk (0);
}
Thus, it seems to me that at least we have a consistency issue, at some
level. Are we already "inadvertently" implementing P0478R0 or I'm
missing something else?!?
Paolo.
next prev parent reply other threads:[~2019-04-12 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 15:21 Paolo Carlini
2019-04-12 10:02 ` Paolo Carlini [this message]
2019-04-12 18:46 ` Jason Merrill
2019-04-15 20:36 ` Paolo Carlini
2019-04-18 17:45 ` 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=a2c97024-39d8-6212-06f3-819419d9bc2e@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).