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 21:06:39 +0000 (GMT) [thread overview] Message-ID: <20220809210639.7D0B63858419@sourceware.org> (raw) https://gcc.gnu.org/g:50d44e73584dc2dd98caa649903c8aefa3b6990e commit 50d44e73584dc2dd98caa649903c8aefa3b6990e Author: Michael Meissner <meissner@linux.ibm.com> Date: Tue Aug 9 17:06:21 2022 -0400 Update ChangeLog.meissner. 2022-08-08 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index c6f47016765..4bc6bdb00a9 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,34 @@ +==================== work097, patch002 + +Rework 128-bit complex multiply and divide. + +This function reworks how the complex multiply and divide built-in functions are +done. Previously we created built-in declarations for doing long double complex +multiply and divide when long double is IEEE 128-bit. The old code also did not +support __ibm128 complex multiply and divide if long double is IEEE 128-bit. + +One of the problems with this approach is that the add_builtin_function would +abort if we used the same name for two different built-in functions. + +This code does not create the built-in declaration. Instead, it uses the +TARGET_MANGLE_DECL_ASSEMBLER_NAME hook to change the name before it is written +out to the assembler file. + +2022-08-09 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000-c.cc (rs6000_cpu_cpp_builtins): Set + building_libgcc. + * 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. + * config/rs6000/rs6000.opt (building_libgcc): New target variable. + ==================== work097, patch001 Allow __ibm128 even if IEEE 128-bit floating point is not supported.
next reply other threads:[~2022-08-09 21:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-09 21:06 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-08-13 2:16 Michael Meissner 2022-08-12 21:19 Michael Meissner 2022-08-12 19:59 Michael Meissner 2022-08-12 4:19 Michael Meissner 2022-08-12 1:12 Michael Meissner 2022-08-11 21:16 Michael Meissner 2022-08-10 7:04 Michael Meissner 2022-08-09 22:32 Michael Meissner 2022-08-09 20:53 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=20220809210639.7D0B63858419@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).