public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/57110] is the use of "uint_fast32_t" in <random> intentional?
Date: Mon, 29 Apr 2013 11:47:00 -0000	[thread overview]
Message-ID: <bug-57110-4-dz9kQg91Q2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57110-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57110

--- Comment #2 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2013-04-29 11:47:54 UTC ---
Understood.
The question should than be escalated to the c++ standard committee

In my opinion the use of a 32-bit unsigned int as storage and return type for a
mersenne_twister_engine
with word_size=32 is wrong (besides being unnecessary and inefficient)

in any case std::mt19937 is just a type alias: users can define their own using
uint32_t in case they care of computational efficiency.


  parent reply	other threads:[~2013-04-29 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 10:20 [Bug libstdc++/57110] New: " vincenzo.innocente at cern dot ch
2013-04-29 10:44 ` [Bug libstdc++/57110] " paolo.carlini at oracle dot com
2013-04-29 11:47 ` vincenzo.innocente at cern dot ch [this message]
2013-04-29 11:50 ` paolo.carlini at oracle dot com

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-57110-4-dz9kQg91Q2@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).