From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Extend std::copy/std::copy_n char* overload to deque iterator
Date: Sat, 23 May 2020 17:37:26 +0100 [thread overview]
Message-ID: <20200523163726.GU2678@redhat.com> (raw)
In-Reply-To: <1f3fe6ef-cd1a-5fad-7d2b-a01a80a37269@gmail.com>
On 22/05/20 22:57 +0200, François Dumont via Libstdc++ wrote:
>On 21/05/20 2:17 pm, Jonathan Wakely wrote:
>>
>>Why is the optimization not done for C++03 mode?
>>
>I did it this way because the new std::copy overload rely on
>std::copy_n implementation details which is a C++11 algo.
>
>
>>It looks like the uses of 'auto' can be reaplced easily, and
>>__enable_if_t<> can be replaced with __gnu_cxx::__enable_if<>::__type.
>>
>But yes, we can indeed provide those implementation details in pre-C++11.
>
>This is what I've done in this new version.
>
>Tested under Linux x86_64 in default c++ mode.
>
>I tried to use CXXFLAGS=-std=c++03 but it doesn't seem to work even if
>I do see the option in build logs. I remember you adivised a different
>approach, can you tell me again ?
See the documentation:
https://gcc.gnu.org/onlinedocs/libstdc++/manual/test.html#test.run.permutations
next prev parent reply other threads:[~2020-05-23 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 7:12 François Dumont
2020-05-15 5:17 ` François Dumont
2020-05-19 19:12 ` François Dumont
2020-05-21 12:17 ` Jonathan Wakely
2020-05-22 20:57 ` François Dumont
2020-05-23 14:02 ` François Dumont
2020-05-23 16:37 ` Jonathan Wakely [this message]
2020-05-24 13:43 ` François Dumont
2020-05-26 11:45 ` François Dumont
2020-06-02 14:20 ` François Dumont
2020-06-02 20:15 ` Jonathan Wakely
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=20200523163726.GU2678@redhat.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/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).