public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gabravier at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/4403] strfry() gives skewed distributions Date: Wed, 21 Sep 2022 17:10:52 +0000 [thread overview] Message-ID: <bug-4403-131-5JW8d2GRaz@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-4403-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=4403 Gabriel Ravier <gabravier at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gabravier at gmail dot com --- Comment #11 from Gabriel Ravier <gabravier at gmail dot com> --- Isn't this fixed ? Looking at current source it appears to have a proper Fisher-Yates shuffle for strfry now -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-09-21 17:10 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-4403-131@http.sourceware.org/bugzilla/> 2010-10-31 17:47 ` [Bug libc/4403] " awreece at gmail dot com 2011-07-26 17:26 ` kirill at shutemov dot name 2012-05-06 18:58 ` aj at suse dot de 2014-02-16 19:36 ` jackie.rosen at hushmail dot com 2014-05-28 19:46 ` schwab at sourceware dot org 2014-06-23 3:42 ` allachan at au1 dot ibm.com 2014-06-24 8:30 ` fweimer at redhat dot com 2014-07-13 22:00 ` coleharrisjohnson at gmail dot com 2015-08-27 22:03 ` [Bug string/4403] " jsm28 at gcc dot gnu.org 2015-09-04 7:17 ` slashtrooll at misc dot lka.org.lu 2022-03-26 22:42 ` sam at gentoo dot org 2022-09-21 17:10 ` gabravier at gmail dot com [this message]
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=bug-4403-131-5JW8d2GRaz@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).