public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "allachan at au1 dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/4403] strfry() gives skewed distributions
Date: Mon, 23 Jun 2014 03:42:00 -0000	[thread overview]
Message-ID: <bug-4403-131-DXEkNws6X3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-4403-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=4403

paxdiablo <allachan at au1 dot ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |allachan at au1 dot ibm.com

--- Comment #10 from paxdiablo <allachan at au1 dot ibm.com> ---
Well, nothing in the doco
(http://www.gnu.org/software/libc/manual/html_node/strfry.html) for strfry()
stated that all combinations would be equally likely. The only mention of
uniform distribution was that it was used to do the swaps themselves, not that
the results would be uniformly distributed.

In any case, when I make stir fry, it's rarely distributed perfectly. Having
said that, Ulrich probably spent more time complaining about the patch than it
would have taken to just put the damn thing in :-)

I have to go with Reuben here. If it's a joke, get rid of it, it has no place
in a serious piece of software. If not, we should be willing to accept patches
that make it better in some way, given any constraints from elsewhere (such as
time needed by maintainers to do it).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-06-23  3:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-4403-131@http.sourceware.org/bugzilla/>
2010-10-31 17:47 ` 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 [this message]
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
2007-04-21 21:36 [Bug libc/4403] New: " aurelien at aurel32 dot net
2007-05-20 20:49 ` [Bug libc/4403] " aurelien at aurel32 dot net
2007-08-22  7:30 ` drepper at redhat dot com
2009-05-09 17:00 ` me at evancarroll dot com
2009-05-10  8:04 ` pasky at suse dot cz
2010-09-16 12:05 ` rrt at sc3d dot org

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-DXEkNws6X3@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: 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).