From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [PATCH] libc: replace lrand's algorithm
Date: Sat, 20 Apr 2024 15:01:45 +0200 [thread overview]
Message-ID: <162AEF1BBB4F9502FA37B39011F4EA0D@felloff.net> (raw)
In-Reply-To: <A6C9292FABA651FDFD2A30B90E48801C@felloff.net>
actually, no. lrand() is fine.
theres no change needed i think:
r = (s[0] + s[1]) >> 33;
note, we shift 33. not 32 that
means the MSB is always 0.
so disregard.
--
cinap
next prev parent reply other threads:[~2024-04-20 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 8:19 Eolien55
2024-03-29 12:39 ` qwx
2024-03-29 16:02 ` Eolien55
2024-04-01 15:47 ` qwx
2024-04-02 14:37 ` Eolien55
2024-04-02 14:52 ` Stanley Lieber
2024-04-02 20:18 ` Eolien55
2024-04-03 9:07 ` qwx
2024-04-03 19:50 ` Ori Bernstein
2024-04-03 19:54 ` Ori Bernstein
2024-04-04 21:00 ` Eolien55
2024-04-20 12:46 ` cinap_lenrek
2024-04-20 12:58 ` cinap_lenrek
2024-04-20 13:01 ` cinap_lenrek [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-29 8:15 Eolien55
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=162AEF1BBB4F9502FA37B39011F4EA0D@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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 NNTP newsgroup(s).