From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 109d8a,232e89dd4cc3c154 X-Google-NewGroupId: yes X-Google-Thread: 1014db,232e89dd4cc3c154 X-Google-NewGroupId: yes X-Google-Thread: 1094ba,232e89dd4cc3c154 X-Google-NewGroupId: yes X-Google-Thread: 101deb,dea70f96af442ea2 X-Google-NewGroupId: yes X-Google-Thread: 103376,232e89dd4cc3c154 X-Google-NewGroupId: yes X-Google-Attributes: gid9ef9b79ae9,gid4516fb5702,gid8d3408f8c3,gidbda4de328f,gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!news.glorb.com!feeder.erje.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: glen herrmannsfeldt Newsgroups: sci.math,comp.lang.c,comp.lang.fortran,comp.lang.pl1,comp.lang.ada Subject: Re: KISS4691, a potentially top-ranked RNG. Date: Fri, 29 Apr 2011 02:34:23 +0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: <4dae2a4b$0$55577$c30e37c6@exi-reader.telstra.net> <4db90113$0$77724$c30e37c6@exi-reader.telstra.net> Injection-Date: Fri, 29 Apr 2011 02:34:23 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="VhYZ3ZDVkI1WvjO/5Jzlvw"; logging-data="5469"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19JqV74H8ThEjdmr/E90Eqa" User-Agent: tin/1.9.6-20100522 ("Lochruan") (UNIX) (Linux/2.6.32-5-amd64 (x86_64)) Cancel-Lock: sha1:S3WwIlFpo7IXqY0Cz1vJjTwyITg= Xref: g2news1.google.com sci.math:217076 comp.lang.c:115331 comp.lang.fortran:38939 comp.lang.pl1:2306 comp.lang.ada:19080 Date: 2011-04-29T02:34:23+00:00 List-Id: In comp.lang.fortran David Bernier wrote: (snip) > All we have now are George Marsaglia's posts and writings. > I know there's now a move on the way to 64-bit processors, > which I take to mean the x86_64 or AMD64 design/instruction set. I have an actual Itanium system, but not so many people do. > In any case, with an executable compiled with a C compiler, > there's the function sizeof, which might be useful > in some cases at run time. Well, sizeof is a compile time constant, but, yes, you can use the value at run time. (snip) > AFAIK, sizeof(unsigned long) can be relied upon to give the size > in 8-bit bytes of a C "unsigned long". No. You need CHAR_BIT to tell how many bits are in a char. It has been known to get to 64 on word addressed 64 bit machines. It must be at least 8, but can be more. -- glen