From: Jason Merrill <jason@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [C++ PATCH] Add __cpp_guaranteed_copy_elision and __cpp_nontype_template_parameter_auto
Date: Mon, 14 Jan 2019 20:07:00 -0000 [thread overview]
Message-ID: <2a516439-5ba8-88f7-a21b-2029ce3e0d8a@redhat.com> (raw)
In-Reply-To: <20190112133651.GU30353@tucnak>
On 1/12/19 8:36 AM, Jakub Jelinek wrote:
> Hi!
>
> So, from what I can understand, __cpp_guaranteed_copy_elision
> is a C++17 P0135R1 feature test macro for a feature we claim to support,
> and __cpp_nontype_template_parameter_auto is a new name for the
> __cpp_template_auto macro (which doesn't appear anymore in the SD-6 lists,
> but clang++ keeps it for backwards compatibility too).
>
> Tested on x86_64-linux, ok for trunk?
>
> 2019-01-12 Jakub Jelinek <jakub@redhat.com>
>
> * c-cppbuiltin.c (c_cpp_builtin): Define __cpp_guaranteed_copy_elision
> and __cpp_nontype_template_parameter_auto. Add a comment that
> __cpp_template_auto is deprecated.
>
> * g++.dg/cpp1z/feat-cxx1z.C: Add tests for
> __cpp_guaranteed_copy_elision and __cpp_nontype_template_parameter_auto
> feature test macros.
> * g++.dg/cpp2a/feat-cxx2a.C: Likewise.
OK.
Jason
prev parent reply other threads:[~2019-01-14 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 13:37 Jakub Jelinek
2019-01-14 20:07 ` 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=2a516439-5ba8-88f7-a21b-2029ce3e0d8a@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).