public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <paolo.carlini@oracle.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Ed Smith-Rowland <3dw4rd@verizon.net>,
	       gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: add uniform on sphere distribution
Date: Sun, 13 Jul 2014 16:56:00 -0000	[thread overview]
Message-ID: <53C2B942.5060502@oracle.com> (raw)
In-Reply-To: <CAOPLpQcSV+U1E6f8g+MWizeB=Ec0_ZJg4gFwTSOErf76BxLeZw@mail.gmail.com>

Hi,

On 07/13/2014 06:44 PM, Ulrich Drepper wrote:
> But your 4th and 7th call example by itself is not a reason. Again, 
> the input exclusively determined by the random numbers. Here, of 
> course, the 4th and 7th use will produce different results. But this 
> is not what the state of the distribution is supposed to capture. For 
> that you'll have to save the state of the RNG as well.
Yes, you are right. Saving the full state of the distribution solves 
only half of my hypothetical problem, but certainly you have to save it 
if you want to, say, reset the RNGs to a common state and get the same 
sequences of numbers after the os << x and is >> y pair.

Paolo.

  reply	other threads:[~2014-07-13 16:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 13:55 Ed Smith-Rowland
2014-07-13 14:12 ` Ulrich Drepper
2014-07-13 14:48   ` Ed Smith-Rowland
2014-07-13 15:47   ` Paolo Carlini
2014-07-13 16:04     ` Ulrich Drepper
2014-07-13 16:12       ` Paolo Carlini
2014-07-13 16:18         ` Ulrich Drepper
2014-07-13 16:29           ` Paolo Carlini
2014-07-13 16:45             ` Ulrich Drepper
2014-07-13 16:56               ` Paolo Carlini [this message]
2014-07-14  7:58               ` Andreas Schwab
2014-07-14  8:18                 ` Paolo Carlini
2014-07-16 11:30                   ` Ed Smith-Rowland
2014-07-16 15:03                     ` Paolo Carlini
2014-07-16 17:38                       ` Ulrich Drepper
  -- strict thread matches above, loose matches on Subject: below --
2014-07-14 10:31 Dominique Dhumieres
2014-07-13  2:01 Ulrich Drepper
2014-07-13  2:06 ` Ulrich Drepper
2014-07-13  9:28 ` Paolo Carlini
2014-07-13 10:04   ` Ulrich Drepper
2014-07-13 10:40     ` Paolo Carlini
2014-07-23 10:05 ` Marc Glisse
2014-07-23 10:44   ` Jonathan Wakely
2014-07-24 22:14     ` Ulrich Drepper
2014-07-24 23:19       ` Jonathan Wakely
2014-08-08 23:24     ` Ulrich Drepper
2014-08-09  7:15       ` Marc Glisse
2014-08-09 11:55         ` Ulrich Drepper
2014-08-09 12:34           ` Marc Glisse
2014-08-09 15:24             ` Ulrich Drepper
2014-08-09 15:33               ` Marc Glisse
2014-08-09 16:55                 ` Ed Smith-Rowland
2014-08-09 16:56                 ` Ulrich Drepper
2014-08-09 17:40                   ` Marc Glisse
2014-08-09 18:00                     ` Ulrich Drepper
2014-08-13  7:36                       ` Bin.Cheng
2014-08-13  7:43                         ` Bin.Cheng
2014-08-13  8:41                         ` Paolo Carlini
2014-08-13 11:25                           ` Paolo Carlini
2014-08-13 11:32                             ` Marc Glisse
2014-08-13 11:40                               ` Paolo Carlini

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=53C2B942.5060502@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=3dw4rd@verizon.net \
    --cc=drepper@gmail.com \
    --cc=gcc-patches@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).