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/work097)] Update ChangeLog.meissner. Date: Tue, 9 Aug 2022 20:53:18 +0000 (GMT) [thread overview] Message-ID: <20220809205318.0EAD73858419@sourceware.org> (raw) https://gcc.gnu.org/g:ea4e99013f4e49199cb35cd13d0a4d06cb90e70d commit ea4e99013f4e49199cb35cd13d0a4d06cb90e70d Author: Michael Meissner <meissner@linux.ibm.com> Date: Tue Aug 9 16:53:03 2022 -0400 Update ChangeLog.meissner. 2022-08-08 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 4904d6ccc45..c6f47016765 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,39 @@ +==================== work097, patch001 + +Allow __ibm128 even if IEEE 128-bit floating point is not supported. + +This set of patches changes the GCC compiler to allow the use of the __ibm128 +keyword if we have IEEE 128-bit floating point support enabled or if long double +is 128-bits. + +In addition, checks for requiring hardware floating point to use __ibm128 have +been removed. This fixes PR target/105534. + +2022-08-09 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + PR target/105534 + * config/rs6000/rs6000-builtins.cc (rs6000_init_builtins): Create + __ibm128 on older machines without IEEE 128-bit support. + * config/rs6000/rs600.cc (init_float128_ibm): Remove checks for hardware + floating point for the IBM 128-bit comparisons. + (rs6000_init_libfuncs): Create IBM 128-bit floating point support even + if we don't support IEEE 128-bit floating point. + (rs6000_scalar_mode_supported_p): Allow __ibm128 even if we don't + support _Float128. + * config/rs6000/rs6000.h (FLOAT128_IBM_P): Remove checks for + -mhard-float. + (TARGET_IBM128): New macro. + * config/rs6000/rs6000.md (@extenddf<mode>2_fprs): Allow IFmode to be + converted even if long double is not 128-bits. + (extenddf<mode>2_vsx): Likewise. + (extendtfif2): Allow conversion if we have __ibm128 but not IEEE 128-bit + floating point. + (trunckftf2): Likewise. + +==================== work097, create branch + 2022-08-08 Michael Meissner <meissner@linux.ibm.com> Clone branch
next reply other threads:[~2022-08-09 20:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-09 20:53 Michael Meissner [this message] 2022-08-09 21:06 Michael Meissner 2022-08-09 22:32 Michael Meissner 2022-08-10 7:04 Michael Meissner 2022-08-11 21:16 Michael Meissner 2022-08-12 1:12 Michael Meissner 2022-08-12 4:19 Michael Meissner 2022-08-12 19:59 Michael Meissner 2022-08-12 21:19 Michael Meissner 2022-08-13 2:16 Michael Meissner
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=20220809205318.0EAD73858419@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).