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/work106)] Update ChangeLog.meissner Date: Wed, 18 Jan 2023 06:12:33 +0000 (GMT) [thread overview] Message-ID: <20230118061233.B76C83858D28@sourceware.org> (raw) https://gcc.gnu.org/g:0da97bd3b7ceaebde67f66362f08b80cfcf399fb commit 0da97bd3b7ceaebde67f66362f08b80cfcf399fb Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Jan 18 01:12:30 2023 -0500 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 2657be8d980..20e6f8343c1 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,4 +1,4 @@ -==================== work106, patch #3 ==================== +==================== work106, patch #4 ==================== PR target/107299: Update IEEE 128-bit types in PowerPC libgcc. @@ -30,7 +30,7 @@ support (_mulkc3, _divkc3, and float128-ifunc) to always be compiled with IEEE 128-bit long double. This is to be type correct, and avoid mismatch declaration errors from the compiler. -2023-01-17 Michael Meissner <meissner@linux.ibm.com> +2023-01-18 Michael Meissner <meissner@linux.ibm.com> PR target/107299 * config/rs6000/_divkc3.c (top level): Require that long double is IEEE @@ -57,10 +57,28 @@ errors from the compiler. (__divkc3_hw): Likewise. (__mulkc3): Likewise. (__divkc3): Likewise. + * config/rs6000/t-rs6000 (fp128_cmuldiv): Add support to build IEEE + 128-bit complex multiply/divide with explicit IEEE-128 long double. + (fp128_cmuldiv_static_obj): Likewise. + (fp128_cmuldiv_shared_obj): Likewise. + (fp128_cmuldiv_obj): Likewise. + (fp128_ppc_funcs): Likewise. + (FP128_CFLAGS_CMULDIV): Likewise. + * config/rs6000/t-rs6000-hw (fp128_hardfp_src): Delete, unused. + (fp128_cmuldiv_funcs): Add support to build IEEE 128-bit complex + multiply/divide with explicit IEEE-128 long double. + (fp128_cmuldiv_static_obj): Likewise. + (fp128_cmuldiv_shared_obj): Likewise. + (fp128_cmuldiv_obj): Likewise. + (fp128_hw_funcs): Likewise. + (fp128_ifunc_funcs): Delete, unused. + (fp128_ifunc_src): Likewise. * libgcc2.h (TFtype): Allow md files to override this. (TCtype): Likewise. * soft-fp/quad.h (TFtype): Likewise. +==================== work106, patch #3 was reverted ==================== + ==================== work106, patch #2 was reverted ==================== ==================== work106, patch #1 was reverted ====================
next reply other threads:[~2023-01-18 6:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-18 6:12 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-18 16:20 Michael Meissner 2023-01-18 8:57 Michael Meissner 2023-01-18 2:39 Michael Meissner 2023-01-18 0:12 Michael Meissner 2023-01-13 0:03 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=20230118061233.B76C83858D28@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).