Le ven. 15 mars 2019 à 19:03, Alex Herbert a écrit :
>
> PS. Did you try this test program to check the size of the unsigned long?
I'm on 64-bits Debian GNU/Linux, so...
sizeof(int) = 4
sizeof(long) = 8
sizeof(unsigned long) = 8
sizeof(uint32_t) = 4
sizeof(double) = 8
[... same as yours, below .
Hi.
Le ven. 15 mars 2019 à 19:00, Alex Herbert a écrit :
>
>
>
> > On 15 Mar 2019, at 17:37, Gilles Sadowski wrote:
> >
> > Hi Alex.
> >
> > Le ven. 15 mars 2019 à 14:08, Alex Herbert a
> > écrit :
> >>
> >> FYI.
> >>
> >>> I am going to update stdin2testu01.c so that it passes all the input b
PS. Did you try this test program to check the size of the unsigned long?
>
>
> The c standard for long states that it can be 32-bits or more! So to check
> what happens on my 64-bit test machine:
>
> #include
> #include
> #include
>
> int main(void){
> printf("sizeof(int) = %d\n", (in
> On 15 Mar 2019, at 17:37, Gilles Sadowski wrote:
>
> Hi Alex.
>
> Le ven. 15 mars 2019 à 14:08, Alex Herbert a écrit
> :
>>
>> FYI.
>>
>>> I am going to update stdin2testu01.c so that it passes all the input bits
>>> to TestU01 and try again.
>>>
>>> I’ve read some of the code and manu
Hi Alex.
Le ven. 15 mars 2019 à 14:08, Alex Herbert a écrit :
>
> FYI.
>
> > I am going to update stdin2testu01.c so that it passes all the input bits
> > to TestU01 and try again.
> >
> > I’ve read some of the code and manual of TestU01 and the values that are
> > returned from the unif01_Gen-
Isn't there a related convo at the Incubator about that?
Anyways, this would be a neat feature for adding mirrors of official
releases. The automatic releases feature for when you make a git tag
can look weird, though, since they're not the actual release
typically.
On Sat, 9 Mar 2019 at 19:16, R
FYI.
> I am going to update stdin2testu01.c so that it passes all the input bits to
> TestU01 and try again.
>
> I’ve read some of the code and manual of TestU01 and the values that are
> returned from the unif01_Gen->GetBits method (unsigned long) are assumed to
> be 32-bit unsigned. So I thi
I think the summary of this thread on outstanding PRs is:
> RNG-82: Add XorShift1024StarPhi generator
> RNG-70: Add new XoShiRo generators
Merge but:
- Ensure those generators with more than one constructor build the same
sequence if the seed data is the same. This is to satisfy package require
> On 14 Mar 2019, at 14:10, Alex Herbert wrote:
>
> Sorry, my earlier message was truncated.
>
> On 13/03/2019 18:31, Gilles Sadowski wrote:
>>
>>> I ran:
>>>
>>> XorShiftXorComposite: XorComposite using XorShift1024Star +
>>> XorShift1024StarPhi with the same seed
>>>
>>> XorShiftSerialComp
