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 target/104253] libgcc missing __floatdiif Date: Sat, 05 Mar 2022 16:23:50 +0000 [thread overview] Message-ID: <bug-104253-4-GEA95qDhV1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104253-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Michael Meissner <meissner@gcc.gnu.org>: https://gcc.gnu.org/g:a1984704a7c2b9be8c89b3381e9c453ccbc5e7bf commit r11-9638-ga1984704a7c2b9be8c89b3381e9c453ccbc5e7bf Author: Michael Meissner <meissner@linux.ibm.com> Date: Sat Mar 5 11:19:43 2022 -0500 Use correct names for __ibm128 if long double is IEEE 128-bit. If you are on a PowerPC system where the default long double is IEEE 128-bit (either through the compiler option -mabi=ieeelongdouble or via the configure option --with-long-double-format=ieee), GCC used the wrong names for some of the conversion functions for the __ibm128 type. Internally, GCC uses IFmode for __ibm128 if long double is IEEE 128-bit, instead of TFmode when long double is IBM 128-bit. This patch adds the missing conversions to prevent the 'if' name from being used. In particular, before the patch, the conversions used were: IFmode to DImode signed: __fixifdi instead of __fixtfdi IFmode to DImode unsigned __fixunsifti instead of __fixunstfti DImode to IFmode signed: __floatdiif instead of __floatditf DImode to IFmode unsigned: __floatundiif instead of __floatunditf 2022-03-05 Michael Meissner <meissner@the-meissners.org> gcc/ PR target/104253 * config/rs6000/rs6000.c (init_float128_ibm): Update the conversion functions used to convert IFmode types. Backport change from 2022-02-14 made on the master branch. gcc/testsuite/ PR target/104253 * gcc.target/powerpc/pr104253.c: New test. Backport change from 2022-02-14 made on the master branch.
next prev parent reply other threads:[~2022-03-05 16:23 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-26 22:22 [Bug target/104253] New: " murphyp at linux dot vnet.ibm.com 2022-01-26 23:31 ` [Bug libgcc/104253] " meissner at gcc dot gnu.org 2022-01-26 23:52 ` joseph at codesourcery dot com 2022-01-26 23:53 ` jakub at gcc dot gnu.org 2022-01-27 19:42 ` meissner at gcc dot gnu.org 2022-01-27 19:45 ` meissner at gcc dot gnu.org 2022-01-28 18:39 ` [Bug target/104253] " jakub at gcc dot gnu.org 2022-01-28 20:30 ` jakub at gcc dot gnu.org 2022-01-28 21:09 ` meissner at gcc dot gnu.org 2022-01-28 22:23 ` meissner at gcc dot gnu.org 2022-01-31 10:30 ` jakub at gcc dot gnu.org 2022-01-31 18:43 ` meissner at gcc dot gnu.org 2022-02-14 22:42 ` cvs-commit at gcc dot gnu.org 2022-02-17 21:59 ` bergner at gcc dot gnu.org 2022-03-05 16:23 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-06 1:16 ` cvs-commit at gcc dot gnu.org 2022-03-06 1:24 ` meissner at gcc dot gnu.org 2022-03-13 18:06 ` ebotcazou at gcc dot gnu.org 2022-03-14 17:03 ` bergner at gcc dot gnu.org 2022-04-06 20:51 ` bergner at gcc dot gnu.org 2022-04-07 10:47 ` ebotcazou at gcc dot gnu.org 2022-04-07 22:25 ` cvs-commit at gcc dot gnu.org 2022-04-11 15:21 ` cvs-commit at gcc dot gnu.org 2022-04-11 17:18 ` cvs-commit at gcc dot gnu.org 2022-04-11 17:26 ` cvs-commit 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-104253-4-GEA95qDhV1@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).