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 16:20:43 +0000 (GMT) [thread overview] Message-ID: <20230118162043.5E3DB385B52E@sourceware.org> (raw) https://gcc.gnu.org/g:b20365c9ee99892240353f84454a93451c107ff8 commit b20365c9ee99892240353f84454a93451c107ff8 Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Jan 18 11:20:40 2023 -0500 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 46 ++++++++++++++-------------------------------- 1 file changed, 14 insertions(+), 32 deletions(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 31893ab4dc9..d926b059004 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,4 +1,4 @@ -==================== work106, patch #6 ==================== +==================== work106, patch #7 ==================== PR target/107299: Fix build issue when long double is IEEE 128-bit @@ -8,13 +8,10 @@ At the moment, we cannot build GCC when the target uses IEEE 128-bit long doubles, such as building the compiler for a native Fedora 36 system. The build dies when it is trying to build the _mulkc3.c and _divkc3 modules. -This patch creates special types for declaring complex IEEE 128-bit multiply and -divide support to use either _Float128 or long double, depending on whether long -double is IBM or IEEE. - -It also uses the correct built-in functions in the libgcc complex IEEE 128-bit -multiply and divide support. This fixes the problems when long double types are -used with explicit f128 built-in functions. +This patch changes libgcc to use long double for the IEEE 128-bit base type if +long double is IEEE 128-bit, and it uses _Float128 otherwise. The built-in +functions are adjusted to be the correct version based on the IEEE 128-bit base +type used. 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 @@ -29,11 +26,6 @@ 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. -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-18 Michael Meissner <meissner@linux.ibm.com> PR target/107299 @@ -41,26 +33,16 @@ errors from the compiler. whether long double is IBM or IEEE. (INFINITY): Likewise. (FABS): Likewise. - (__divkc3): Use either _Float128 or long double for the types to match - whether long double is IBM or IEEE. - * config/rs6000/_mulkc3.c (COPYSIGN): Use the correct built-in based on - whether long double is IBM or IEEE. + * config/rs6000/_mulkc3.c (COPYSIGN): Likewise. (INFINITY): Likewise. - (__mulkc3): Use either _Float128 or long double for the types to match - whether long double is IBM or IEEE. - * config/rs6000/float128-ifunc.c (__mulkc3): Use either _Float128 or - long double for the types to match whether long double is IBM or IEEE. - (__divkc3): Likewise. - * config/rs6000/quad-float128.h (TC): Define to switch complex IEEE - 128-bit type in machine independent code via mode attribute. - (TFtype_cmuldiv): New macro. - (TCtype_cmuldiv): Likewise. - (__mulkc3_sw): Use TFtype_cmuldiv and TCtype_cmuldiv. - (__divkc3_sw): Likewise. - (__mulkc3_hw): Likewise. - (__divkc3_hw): Likewise. - (__mulkc3): Likewise. - (__divkc3): Likewise. + * config/rs6000/quad-float128.h (TF): Remove definition. + (TFtype): Define to be long double or _Float128. + (TCtype): Define to be _Complex long double or _Complex _Float128. + * libgcc2.h (TFtype): Allow machine config files to override this. + (TCtype): Likewise. + * soft-fp/quad.h (TFtype): Likewise. + +==================== work106, patch #6 was reverted ==================== ==================== work106, patch #5 was reverted ====================
next reply other threads:[~2023-01-18 16:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-18 16:20 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-18 8:57 Michael Meissner 2023-01-18 6:12 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=20230118162043.5E3DB385B52E@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).