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 02:39:27 +0000 (GMT) [thread overview] Message-ID: <20230118023927.1DC843858D28@sourceware.org> (raw) https://gcc.gnu.org/g:e985cdabfc2a5196aa49c9410a9efbfb7992a3e2 commit e985cdabfc2a5196aa49c9410a9efbfb7992a3e2 Author: Michael Meissner <meissner@linux.ibm.com> Date: Tue Jan 17 21:39:24 2023 -0500 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 67 ++++++++++++++++++++++---------------------------- 1 file changed, 29 insertions(+), 38 deletions(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index a721c02003c..2657be8d980 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,22 +1,6 @@ -==================== work106, patch #2 ==================== +==================== work106, patch #3 ==================== -PR target/107299: Use _Float128 and _Complex _Float128 for PowerPC libgcc IEEE 128-bit - -2023-01-17 Michael Meissner <meissner@linux.ibm.com> - - PR target/107299 - * config/rs6000/quad-float128.h (TF): Remove definition. - (TFtype): New macro, use _Float128. - (TCtype): Change to macro, use _Complex _Float128. - (__mulkc3): Remove declaration. - (__divkc3): Likewise. - * libgcc2.h (TFtype): Allow md files to override this. - (TCtype): Likewise. - * soft-fp/quad.h (TFtype): Likewise. - -==================== work106, patch #1 was reverted ==================== - -PR target/107299: Update IEEE 128-bit types for PowerPC libgcc +PR target/107299: Update IEEE 128-bit types in PowerPC libgcc. This patch updates the IEEE 128-bit types in libgcc. @@ -28,10 +12,6 @@ This patch changes the IEEE 128-bit type (TFtype) in the IEEE 128-bit support to use either _Float128 or long double. Previously we would use the __float128 type. In addition, the TCtype will use the same type along with _Complex. -I changed the libgcc build so that the IEEE 128-bit support is now compiled -with -mabi=ieeelongdouble. For the _mulkc3 and _divkc3, I explicitly use long -double and long double _Complex to avoid type mismatch errors. - While it is desirable to ultimately have __float128 and _Float128 use the same internal type and mode within GCC, at present if you use the option -mabi=ieeelongdouble, the __float128 type will use the long double type. We @@ -45,35 +25,46 @@ fix the compiler at some point, but right now, this is preventing people on Fedora 36 systems from building compilers where the default long double is IEEE 128-bit. -2023-01-12 Michael Meissner <meissner@linux.ibm.com> +I changed the three functions that deal with complex multiply and complex divide +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> PR target/107299 - * config/rs6000/_divkc3.c (toplevel): Add assertion for building with - -mabi=ieeelongdouble. Remove code supporting -mabi=ibmlongdouble. - (COPYSIGN): Use the long double built-in. + * config/rs6000/_divkc3.c (top level): Require that long double is IEEE + 128-bit. + (COPYSIGN): Use long double built-in. (INFINITY): Likewise. (FABS): Likewise. - * config/rs6000/_mulkc3.c (toplevel): Add assertion for building with - -mabi=ieeelongdouble. - (COPYSIGN): Use the long double built-in. + (RBIG): Use TFmode constants, not KFmode. + (RMIN): Likewise. + (RMIN2): Likewise. + (RMINSCAL): Likewise. + (RMAX2): Likewise. + * config/rs6000/_mulkc3.c (top level): Require that long double is IEEE + 128-bit. + (COPYSIGN): Use long double built-in. (INFINITY): Likewise. - * config/rs6000/float128-ifunc.c (toplevel): Add assertion for building - with -mabi=ieeelongdouble. - * config/rs6000/quad-float128.h (TF): Delete definition. - (TFtype): Define to be _Float128 or long double. - (TCtype): Define to be _Complex _Float128 or _Complex long double. - (__mulkc3_sw): Only declare function if -mabi=ieeelongdouble. + * config/rs6000/quad-float128.h (TF): Remove definition. + (TFtype): New macro, use _Float128 or long double. + (TCtype): Change to macro, use _Complex _Float128 or _Complex long + double. + (__mulkc3_sw): Only declare if long double is IEEE 128-bit. (__divkc3_sw): Likewise. (__mulkc3_hw): Likewise. (__divkc3_hw): Likewise. (__mulkc3): Likewise. (__divkc3): Likewise. - * config/rs6000/t-float128 (FP128_CFLAGS_SW): Add -mabi=ieeelongdouble. - * config/rs6000/t-float128-hw (FP128_CFLAGS_HW): Likewise. - * libgcc2.h (TFtype): Allow MD code to override definition. + * libgcc2.h (TFtype): Allow md files to override this. (TCtype): Likewise. * soft-fp/quad.h (TFtype): Likewise. +==================== work106, patch #2 was reverted ==================== + +==================== work106, patch #1 was reverted ==================== + ==================== work106, branch head ==================== 2023-01-12 Michael Meissner <meissner@linux.ibm.com>
next reply other threads:[~2023-01-18 2:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-18 2:39 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 6:12 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=20230118023927.1DC843858D28@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).