From: Jason Merrill <jason@redhat.com>
To: Ville Voutilainen <ville.voutilainen@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [C++ PATCH] PR c++/80812
Date: Wed, 31 May 2017 20:37:00 -0000 [thread overview]
Message-ID: <a76948ab-072e-7f69-b4ab-ad700862d0c1@redhat.com> (raw)
In-Reply-To: <CAFk2RUbhjh3RGDOEurUrF6H5j95VyMXR3F43noDij0mD5Q3Gaw@mail.gmail.com>
On 05/25/2017 05:29 AM, Ville Voutilainen wrote:
> Tested on Linux-x64, running full suite on Linux-ppc64. It seems fitting
> to put the test into the library tests, we don't have separate tests
> on the front-end side for __is_constructible, so I think adding such
> would be a separate job.
>
> 2017-05-25 Ville Voutilainen <ville.voutilainen@gmail.com>
>
> cp/
>
> PR c++/80812
> * method.c (constructible_expr): Strip array types before calling
> build_value_init.
OK.
Jason
prev parent reply other threads:[~2017-05-31 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 9:52 Ville Voutilainen
2017-05-31 20:37 ` Jason Merrill [this message]
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=a76948ab-072e-7f69-b4ab-ad700862d0c1@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=ville.voutilainen@gmail.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).