public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Eelis <eelis@eelis.net>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, libstdc++] std::shuffle: Generate two swap positions at a time if possible
Date: Tue, 03 May 2016 12:39:00 -0000	[thread overview]
Message-ID: <CAH6eHdTnASg7A5USA_sTAHXPfUFmkrZvF27tZUJhj5ywwDVDag@mail.gmail.com> (raw)
In-Reply-To: <ng53cl$4iu$2@ger.gmane.org>

ENOPATCH

On 1 May 2016 at 15:21, Eelis <eelis@eelis.net> wrote:
> Sorry, forgot to include the libstdc++ list.
>
> On 2016-05-01 16:18, Eelis wrote:
>>
>> Hi,
>>
>> The attached patch optimizes std::shuffle for the very common case
>> where the generator range is large enough that a single invocation
>> can produce two swap positions.
>>
>> This reduces the runtime of the following testcase by 37% on my machine:
>>
>>      int main()
>>      {
>>          std::mt19937 gen;
>>
>>          std::vector<int> v;
>>          v.reserve(10000);
>>          for (int i = 0; i != 10000; ++i)
>>          {
>>              v.push_back(i);
>>              std::shuffle(v.begin(), v.end(), gen);
>>          }
>>
>>          std::cout << v.front() << '\n';
>>      }
>>
>> Thoughts?
>>
>> Thanks,
>>
>> Eelis
>>
>
>

  reply	other threads:[~2016-05-03 12:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01 14:18 Eelis
2016-05-01 14:30 ` Eelis
2016-05-03 12:39   ` Jonathan Wakely [this message]
2016-05-03 14:42     ` Eelis van der Weegen
2016-05-25 19:54       ` Eelis
2016-05-25 20:45         ` Eelis
2016-08-31 12:45       ` Jonathan Wakely
2016-09-01 15:14         ` Jonathan Wakely
2016-09-01 15:27           ` Marc Glisse
2016-09-01 15:35             ` Jonathan Wakely
2016-09-01 15:31           ` Eelis van der Weegen
2016-09-01 15:37             ` Jonathan Wakely
2016-09-02 18:20         ` Eelis van der Weegen
2016-09-02 18:53           ` Eelis
2016-09-02 19:27             ` Eelis
2016-10-14 19:42             ` 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=CAH6eHdTnASg7A5USA_sTAHXPfUFmkrZvF27tZUJhj5ywwDVDag@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=eelis@eelis.net \
    --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).