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/dmf011)] Update ChangeLog.meissner Date: Wed, 15 Mar 2023 19:25:44 +0000 (GMT) [thread overview] Message-ID: <20230315192544.083E23858C83@sourceware.org> (raw) https://gcc.gnu.org/g:e4c7bfa3cb71af2318ddc0fc2adba723fc97dc53 commit e4c7bfa3cb71af2318ddc0fc2adba723fc97dc53 Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Mar 15 15:25:40 2023 -0400 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 9178952b46a..e2574d720d6 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,38 @@ +==================== Branch dmf011, patch #1 ==================== + +Rework 128-bit complex multiply and divide. + +This patch reworks how the complex multiply and divide built-in functions are +done. Previously GCC created built-in declarations for doing long double complex +multiply and divide when long double is IEEE 128-bit. However, it did not +support __ibm128 complex multiply and divide if long double is IEEE 128-bit. + +This code does not create the built-in declaration with the changed name. +Instead, it uses the TARGET_MANGLE_DECL_ASSEMBLER_NAME hook to change the name +before it is written out to the assembler file like it now does for all of the +other long double built-in functions. + +2023-03-15 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + PR target/109067 + * config/rs6000/rs6000.cc (create_complex_muldiv): Delete. + (init_float128_ieee): Delete code to switch complex multiply and divide + for long double. + (complex_multiply_builtin_code): New helper function. + (complex_divide_builtin_code): Likewise. + (rs6000_mangle_decl_assembler_name): Add support for mangling the name + of complex 128-bit multiply and divide built-in functions. + +gcc/testsuite/ + + PR target/109067 + * gcc.target/powerpc/divic3-1.c: New test. + * gcc.target/powerpc/divic3-2.c: Likewise. + * gcc.target/powerpc/mulic3-1.c: Likewise. + * gcc.target/powerpc/mulic3-2.c: Likewise. + ==================== Branch dmf011, baseline ==================== 2023-03-15 Michael Meissner <meissner@linux.ibm.com>
next reply other threads:[~2023-03-15 19:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-15 19:25 Michael Meissner [this message] 2023-03-15 20:44 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=20230315192544.083E23858C83@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).