From: Pedro Alves <palves@redhat.com>
To: Jason Merrill <jason@redhat.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Cc: Ville Voutilainen <ville.voutilainen@gmail.com>
Subject: Re: C++ PATCH for P0135, C++17 guaranteed copy elision
Date: Wed, 05 Oct 2016 23:16:00 -0000 [thread overview]
Message-ID: <68323906-2179-82c7-98f9-0fd2ddb40ab5@redhat.com> (raw)
In-Reply-To: <CADzB+2nUgkOKbdMM_XXL4e53HQ712TLmRszvwEJQmm591UobaQ@mail.gmail.com>
On 10/05/2016 11:57 PM, Jason Merrill wrote:
> --- a/gcc/c-family/c-opts.c
> +++ b/gcc/c-family/c-opts.c
> @@ -1579,6 +1579,7 @@ set_std_cxx1z (int iso)
> flag_isoc94 = 1;
> flag_isoc99 = 1;
> flag_isoc11 = 1;
> + flag_elide_constructors = 2;
> cxx_dialect = cxx1z;
> lang_hooks.name = "GNU C++14"; /* Pretend C++14 till standarization. */
Does -fno-elide-constructors have any effect in C++17 mode?
Should it perhaps be an error, or ignored?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-05 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 22:57 Jason Merrill
2016-10-05 23:16 ` Pedro Alves [this message]
2016-10-05 23:22 ` Jason Merrill
2016-10-06 21:26 ` Jason Merrill
2016-10-08 16:27 ` 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=68323906-2179-82c7-98f9-0fd2ddb40ab5@redhat.com \
--to=palves@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--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).