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/work104)] Update ChangeLog.meissner. Date: Sat, 7 Jan 2023 01:35:25 +0000 (GMT) [thread overview] Message-ID: <20230107013525.1E3F33858D33@sourceware.org> (raw) https://gcc.gnu.org/g:e5103fa74ff213c3e5b0a06662e074dac1c88f32 commit e5103fa74ff213c3e5b0a06662e074dac1c88f32 Author: Michael Meissner <meissner@linux.ibm.com> Date: Fri Jan 6 20:33:55 2023 -0500 Update ChangeLog.meissner. 2023-01-06 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 61 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 61 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index ca8b890ea31..64cd2c02fb7 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,4 +1,63 @@ +==================== Patch #22, work104 branch ==================== + +Update float 128-bit conversions, PR target/107299. + +This patch fixes two tests that are still failing when long double is IEEE +128-bit after the previous 2 patches for PR target/107299 have been applied. +The tests are: + + gcc.target/powerpc/convert-fp-128.c + gcc.target/powerpc/pr85657-3.c + +This patch is a rewrite of the patch submitted on August 18th: + +| https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599988.html + +This patch reworks the conversions between 128-bit binary floating point types. +Previously, we would call rs6000_expand_float128_convert to do all conversions. +Now, we only define the conversions between the same representation that turn +into a NOP. The appropriate extend or truncate insn is generated, and after +register allocation, it is converted to a move. + +This patch also fixes two places where we want to override the external name +for the conversion function, and the wrong optab was used. Previously, +rs6000_expand_float128_convert would handle the move or generate the call as +needed. Now, it lets the machine independent code generate the call. But if +we use the machine independent code to generate the call, we need to update the +name for two optabs where a truncate would be used in terms of converting +between the modes. This patch updates those two optabs. + +This patch was previously submitted on December 14th, 2022. This patch changes +one built-in function from a FLOAT_TRUNCATE to a FLOAT_EXTEND, which is needed +by the previous patch to genmodes.cc to allow allow the same precision to be +used for various modes. + +2022-01-06 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + PR target/107299 + * config/rs6000/rs6000.cc (init_float128_ieee): Use the correct + float_extend or float_truncate optab based on how the machine converts + between IEEE 128-bit and IBM 128-bit. + * config/rs6000/rs6000.md (IFKF): Delete. + (IFKF_reg): Delete. + (extendiftf2): Rewrite to be a move if IFmode and TFmode are both IBM + 128-bit. Do not run if TFmode is IEEE 128-bit. + (extendifkf2): Delete. + (extendtfkf2): Delete. + (extendtfif2): Delete. + (trunciftf2): Delete. + (truncifkf2): Delete. + (trunckftf2): Delete. + (extendkftf2): Implement conversion of IEEE 128-bit types as a move. + (trunctfif2): Delete. + (trunctfkf2): Implement conversion of IEEE 128-bit types as a move. + (extend<mode>tf2_internal): Delete. + (extendtf<mode>2_internal): Delete. + ==================== Patch #21, work104 branch ==================== + Allow for FP types with the same precision. This patch allows 2 or more floating point modes to have the same precision. @@ -53,6 +112,7 @@ gcc/ * machmode.def (FRACTIONAL_FLOAT_MODE_NO_WIDEN): Document. ==================== Patch #20, work104 branch ==================== + Rework 128-bit complex multiply and divide. This patch reworks how the complex multiply and divide built-in functions are @@ -123,6 +183,7 @@ gcc/testsuite/ * gcc.target/powerpc/mulic3-2.c: Likewise. ==================== Basline ==================== + 2023-01-03 Michael Meissner <meissner@linux.ibm.com> Clone branch
next reply other threads:[~2023-01-07 1:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-07 1:35 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-10 20:05 Michael Meissner 2023-01-10 6:02 Michael Meissner 2023-01-10 4:20 Michael Meissner 2023-01-09 20:42 Michael Meissner 2023-01-09 19:47 Michael Meissner 2023-01-07 1:17 Michael Meissner 2023-01-06 23:14 Michael Meissner 2023-01-06 20:10 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=20230107013525.1E3F33858D33@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).