public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "richard at netbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/63332] problem with VERIFY in  ext/random/k_distribution/operators/serialize.cc execution test
Date: Thu, 25 Sep 2014 16:04:00 -0000	[thread overview]
Message-ID: <bug-63332-4-fVGKCZx8qy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63332-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63332

--- Comment #5 from Richard PALO <richard at netbsd dot org> ---
By the way, in gdb, here are the complete u and v variables after
serialisation:

gdb) p u
$1 = {_M_param = {_M_lambda = 2, _M_mu = 1.5, _M_nu = 3}, _M_gd1 = {
    _M_param = {_M_alpha = 2, _M_beta = 0.5, _M_malpha = 2, 
      _M_a2 = 0.25819888974716108}, _M_nd = {_M_param = {_M_mean = 0, 
        _M_stddev = 1}, _M_saved = -1.0868180442613568, 
      _M_saved_available = true}}, _M_gd2 = {_M_param = {_M_alpha = 3, 
      _M_beta = 0.5, _M_malpha = 3, _M_a2 = 0.20412414523193152}, _M_nd = {
      _M_param = {_M_mean = 0, _M_stddev = 1}, _M_saved = 0.18913187340436784, 
      _M_saved_available = true}}}
(gdb) p v
$2 = {_M_param = {_M_lambda = 2, _M_mu = 1.5, _M_nu = 3}, _M_gd1 = {
    _M_param = {_M_alpha = 2, _M_beta = 0.5, _M_malpha = 2, 
      _M_a2 = 0.25819888974716108}, _M_nd = {_M_param = {_M_mean = 0, 
        _M_stddev = 1}, _M_saved = -1.0868180442613568, 
      _M_saved_available = true}}, _M_gd2 = {_M_param = {_M_alpha = 3, 
      _M_beta = 0.5, _M_malpha = 3, _M_a2 = 0.20412414523193152}, _M_nd = {
      _M_param = {_M_mean = 0, _M_stddev = 1}, _M_saved = 0.1891318734043678, 
      _M_saved_available = true}}}

I notice _M_saved in v is truncated by 1 (the trailing '4')...
that is, 16 and not 17 digits after the decimal are copied.


  parent reply	other threads:[~2014-09-25 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 13:35 [Bug testsuite/63332] New: " richard at netbsd dot org
2014-09-22 13:37 ` [Bug testsuite/63332] " richard at netbsd dot org
2014-09-25 10:06 ` redi at gcc dot gnu.org
2014-09-25 10:14 ` [Bug libstdc++/63332] " redi at gcc dot gnu.org
2014-09-25 15:30 ` richard at netbsd dot org
2014-09-25 16:04 ` richard at netbsd dot org [this message]
2014-09-25 16:08 ` richard at netbsd dot org
2014-09-25 16:18 ` redi at gcc dot gnu.org
2014-11-16  7:05 ` richard at netbsd dot org
2014-11-16 14:35 ` redi at gcc dot gnu.org
2020-10-08 14:05 ` redi at gcc dot gnu.org
2020-10-11 11:04 ` ro at CeBiTec dot Uni-Bielefeld.DE

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-63332-4-fVGKCZx8qy@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).