public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/57920] [c++11] Linux: std::random_device reads too much from /dev/urandom
Date: Sun, 21 Jul 2013 20:40:00 -0000 [thread overview]
Message-ID: <bug-57920-4-w4TVqvdv34@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57920-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57920
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2013-07-21
Assignee|unassigned at gcc dot gnu.org |paolo.carlini at oracle dot com
Ever confirmed|0 |1
--- Comment #3 from Paolo Carlini <paolo.carlini at oracle dot com> ---
I'm going to attach a patchlet which does the trick (fread -> read) for me.
Note I'm on purpose disabling the use of __builtin_ia32_rdrand32_step on my
x86_64 machine, the undef would not be in the committed patch of course.
It would be great if you could test the change on your machines (in 4.7.x just
change random.h, no need to rebuild) and confirm that everything is fine.
next prev parent reply other threads:[~2013-07-21 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 15:33 [Bug libstdc++/57920] New: " f.heckenbach@fh-soft.de
2013-07-21 19:55 ` [Bug libstdc++/57920] " paolo.carlini at oracle dot com
2013-07-21 19:56 ` paolo.carlini at oracle dot com
2013-07-21 20:40 ` paolo.carlini at oracle dot com [this message]
2013-07-21 20:41 ` paolo.carlini at oracle dot com
2013-07-22 12:31 ` f.heckenbach@fh-soft.de
2013-07-22 12:33 ` f.heckenbach@fh-soft.de
2013-07-22 12:36 ` paolo.carlini at oracle dot com
2013-07-22 15:25 ` paolo.carlini at oracle dot com
2014-02-11 21:36 ` gnu at binarywings dot net
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-57920-4-w4TVqvdv34@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).