public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98384] [11 Regression] new test case 20_util/to_chars/long_double.cc in r11-6249 fails on powerpc64 BE Date: Tue, 23 Feb 2021 02:49:55 +0000 [thread overview] Message-ID: <bug-98384-4-nGKYXiD1sL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98384-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98384 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:198c56052ea8cce4196e60c0dc3187bf3d67a786 commit r11-7337-g198c56052ea8cce4196e60c0dc3187bf3d67a786 Author: Patrick Palka <ppalka@redhat.com> Date: Mon Feb 22 21:49:25 2021 -0500 libstdc++: Fix endianness issue with IBM long double [PR98384] The code in std::to_chars for extracting the high- and low-order parts of an IBM long double value does the right thing on powerpc64le, but not on powerpc64be. This patch makes the extraction endian-agnostic, which fixes the execution FAIL of to_chars/long_double.cc on powerpc64be. libstdc++-v3/ChangeLog: PR libstdc++/98384 * src/c++17/floating_to_chars.cc (get_ieee_repr): Extract the high- and low-order parts from an IBM long double value in an endian-agnostic way.
next prev parent reply other threads:[~2021-02-23 2:49 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-18 21:39 [Bug libstdc++/98384] New: " seurer at gcc dot gnu.org 2020-12-21 20:28 ` [Bug libstdc++/98384] " ppalka at gcc dot gnu.org 2020-12-22 9:23 ` ro at gcc dot gnu.org 2021-01-05 9:10 ` [Bug libstdc++/98384] [11 Regression] " rguenth at gcc dot gnu.org 2021-01-07 13:04 ` iains at gcc dot gnu.org 2021-01-07 15:42 ` ppalka at gcc dot gnu.org 2021-01-07 16:41 ` iains at gcc dot gnu.org 2021-01-07 17:42 ` cvs-commit at gcc dot gnu.org 2021-01-07 17:55 ` ppalka at gcc dot gnu.org 2021-01-08 9:30 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-01-12 16:35 ` ppalka at gcc dot gnu.org 2021-01-14 11:13 ` rguenth at gcc dot gnu.org 2021-02-12 15:02 ` jakub at gcc dot gnu.org 2021-02-23 2:49 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-23 16:55 ` ppalka at gcc dot gnu.org 2021-02-24 9:58 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-02-24 15:14 ` ppalka at gcc dot gnu.org 2021-02-24 15:42 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-02-24 15:48 ` jakub at gcc dot gnu.org 2021-02-24 16:16 ` ppalka at gcc dot gnu.org 2021-02-24 16:26 ` iains at gcc dot gnu.org 2021-02-24 16:45 ` ppalka at gcc dot gnu.org 2021-02-24 17:26 ` cvs-commit at gcc dot gnu.org 2021-02-27 16:17 ` iains at gcc dot gnu.org 2021-02-27 16:49 ` dje at gcc dot gnu.org 2021-03-03 14:28 ` ppalka at gcc dot gnu.org 2021-03-05 2:37 ` dje at gcc dot gnu.org 2021-03-08 17:42 ` ppalka at gcc dot gnu.org 2021-03-08 17:53 ` schwab@linux-m68k.org 2021-03-08 19:27 ` dje at gcc dot gnu.org 2021-03-08 21:09 ` iains at gcc dot gnu.org 2021-03-08 21:24 ` iains at gcc dot gnu.org 2021-03-09 9:55 ` iains at gcc dot gnu.org 2021-03-10 14:28 ` ppalka at gcc dot gnu.org 2021-03-10 14:51 ` ppalka at gcc dot gnu.org 2021-04-08 15:11 ` cvs-commit at gcc dot gnu.org 2021-04-08 15:22 ` [Bug libstdc++/98384] new test case 20_util/to_chars/long_double.cc in r11-6249 fails ppalka at gcc dot gnu.org 2021-04-08 16:22 ` redi at gcc dot gnu.org 2021-04-27 11:39 ` jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:03 ` jakub 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-98384-4-nGKYXiD1sL@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: linkBe 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).