public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103387] powerpc64le: segmentation fault on std::cout with ieee128 long double variable
Date: Tue, 28 Mar 2023 15:00:37 +0000	[thread overview]
Message-ID: <bug-103387-4-akFNooVns5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103387-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
And that's because we're using the ostream's cached _M_num_put but that is the
wrong one:

(gdb) step
std::basic_ostream<char, std::char_traits<char> >::_M_insert<__ieee128>
(this=0x101c0900 <std::cout>, __v=0.100000000000000000000000000000000005)
    at
/home/test/build/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/bits/ostream.tcc:66
66              sentry __cerb(*this);
(gdb) n
67              if (__cerb)
(gdb) 
69                  ios_base::iostate __err = ios_base::goodbit;
(gdb) 
72                      const __num_put_type& __np =
__check_facet(this->_M_num_put);
(gdb) p _M_num_put
$18 = (const std::basic_ios<char, std::char_traits<char> >::__num_put_type *)
0x101c1f98 <(anonymous namespace)::num_put_c>

  parent reply	other threads:[~2023-03-28 15:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 17:22 [Bug libstdc++/103387] New: " maxiwell at gmail dot com
2021-11-23 18:32 ` [Bug libstdc++/103387] " meissner at gcc dot gnu.org
2021-11-23 21:21 ` redi at gcc dot gnu.org
2021-11-24 22:37 ` tuliom at ascii dot art.br
2022-05-06  8:31 ` jakub at gcc dot gnu.org
2023-03-23 19:01 ` bergner at gcc dot gnu.org
2023-03-28  9:16 ` redi at gcc dot gnu.org
2023-03-28 14:54 ` redi at gcc dot gnu.org
2023-03-28 15:00 ` redi at gcc dot gnu.org [this message]
2023-03-28 16:48 ` redi at gcc dot gnu.org
2023-03-28 23:18 ` cvs-commit at gcc dot gnu.org
2023-03-28 23:19 ` redi at gcc dot gnu.org
2023-04-20 13:57 ` cvs-commit at gcc dot gnu.org
2023-04-20 16:38 ` redi at gcc dot gnu.org
2023-04-21 15:01 ` cvs-commit at gcc dot gnu.org
2023-04-21 15:03 ` redi at gcc dot gnu.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-103387-4-akFNooVns5@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).