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 09:16:02 +0000	[thread overview]
Message-ID: <bug-103387-4-yqsbqhijr3@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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2021-11-23 00:00:00         |2023-3-28

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I thought it was, but no, it seems to still crash:

$ ~/gcc/13/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/home/test/gcc/13/bin/g++
COLLECT_LTO_WRAPPER=/home/test/gcc/13/libexec/gcc/powerpc64le-unknown-linux-gnu/13.0.1/lto-wrapper
Target: powerpc64le-unknown-linux-gnu
Configured with: /home/test/src/gcc/configure --enable-languages=c++
--disable-bootstrap --prefix=/home/test/gcc/13
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.1 20230327 (experimental) (GCC) 
$ ~/gcc/13/bin/g++ d.cc -mabi=ieeelongdouble -Wl,-rpath,$HOME/gcc/13/lib64 
$ ldd ./a.out
        linux-vdso64.so.1 (0x00007fffa0fa0000)
        libstdc++.so.6 => /home/test/gcc/13/lib64/libstdc++.so.6
(0x00007fffa0c00000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fffa0ab0000)
        libgcc_s.so.1 => /home/test/gcc/13/lib64/libgcc_s.so.1
(0x00007fffa0a50000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fffa0600000)
        /lib64/ld64.so.2 (0x00007fffa0fb0000)
$ ./a.out
Segmentation fault (core dumped)

GCC is built with the implied default of --with-long-double-format=ibm and the
testcase is built with -mabi=ieeelongdouble

  parent reply	other threads:[~2023-03-28  9:16 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 [this message]
2023-03-28 14:54 ` redi at gcc dot gnu.org
2023-03-28 15:00 ` redi at gcc dot gnu.org
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-yqsbqhijr3@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).