public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/meissner/heads/work078)] Use correct names for __ibm128 if long double is IEEE 128-bit. Date: Tue, 8 Feb 2022 21:46:56 +0000 (GMT) [thread overview] Message-ID: <20220208214656.389A93858424@sourceware.org> (raw) https://gcc.gnu.org/g:71a7116e72859825a419efd6971a3bfff8f25697 commit 71a7116e72859825a419efd6971a3bfff8f25697 Author: Michael Meissner <meissner@linux.ibm.com> Date: Tue Feb 8 16:46:01 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, GCC will use the wrong names for some of the conversion functions for the __ibm128 type. What is happening is when the defult long double is IEEE 128-bit, the various convert, truncation, and extend functions did not specify a default name for the conversion. The machine indepentent portions of the compiler would construct a call with an 'if' name (IFmode being the mode for IBM 128-bit floating point). This patch specifies to use the tradiational 'tf' name for these conversion functions. 2022-02-08 Michael Meissner <meissner@the-meissners.org> gcc/ PR target/104253 * config/rs6000/rs6000.cc (init_float128_ibm): Use the TF names for builtin conversions between __ibm128 and DImode when long double uses the IEEE 128-bit format. gcc/testsuite/ PR target/104253 * gcc.target/powerpc/pr104253.c: New test. Diff: --- gcc/config/rs6000/rs6000.cc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc index e2d94421ae9..f56cf66313a 100644 --- a/gcc/config/rs6000/rs6000.cc +++ b/gcc/config/rs6000/rs6000.cc @@ -10984,6 +10984,12 @@ init_float128_ibm (machine_mode mode) set_conv_libfunc (trunc_optab, DDmode, mode, "__dpd_trunctfdd"); set_conv_libfunc (sext_optab, TDmode, mode, "__dpd_extendtftd"); + set_conv_libfunc (sfix_optab, DImode, mode, "__fixtfdi"); + set_conv_libfunc (ufix_optab, DImode, mode, "__fixunstfdi"); + + set_conv_libfunc (sfloat_optab, mode, DImode, "__floatditf"); + set_conv_libfunc (ufloat_optab, mode, DImode, "__floatunditf"); + if (TARGET_POWERPC64) { set_conv_libfunc (sfix_optab, TImode, mode, "__fixtfti");
reply other threads:[~2022-02-08 21:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220208214656.389A93858424@sourceware.org \ --to=meissner@gcc.gnu.org \ --cc=gcc-cvs@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).