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 22:32:18 +0000 (GMT) [thread overview] Message-ID: <20220809223218.CCE3D385801A@sourceware.org> (raw) https://gcc.gnu.org/g:3a43994f4876237e5339e1b50407990c90a18fc6 commit 3a43994f4876237e5339e1b50407990c90a18fc6 Author: Michael Meissner <meissner@linux.ibm.com> Date: Tue Aug 9 18:32:02 2022 -0400 Update ChangeLog.meissner. 2022-08-08 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 4bc6bdb00a9..d660cbf6974 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,38 @@ +==================== work097, patch003 + +Use _Float128 type for __float128. + +In the past if the long double type was IEEE 128-bit, the __float128 type would +use the long double type, and TFmode would be used for the mode for both +_Float128 and long double types. + +This patch always uses the _Float128 type for __float128, and it always uses +KFmode for the mode. Right now, a similar change for __ibm128 has not been +made. + +In making these changes, I noticed that there was an internal tree for holding +the __float128 type. This code removes that internal tree variable. + +2022-08-09 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000-builtin.cc (rs6000_type_string): Use + float128_type_node, not ieee128_float_type_mode. + (rs6000_init_builtins): Always use the _Float128 type for the __float128 + keyword. Do not use the long double type. + * config/rs6000/rs6000-c.cc (rs6000_target_modify_macros): Use + float128_type_node, not ieee128_float_type_mode. Simplify if + statements. + (rs6000_cpu_cpp_builtins): Delete ieee128_float_type_mode. + * config/rs6000/rs6000.cc (rs6000_libgcc_floating_mode_supported_p): + Always use KFmode for _Float128 and __float128. + (rs6000_floatn_mode): Likewise. + (rs6000_c_mode_for_suffix): Always use KFmode for _Float128 and + __float128. Add 'w' and 'W' suffix for __ibm128 constants. + * config/rs6000/rs6000.h (RS6000_BTI_ieee128_float): Delete. + (ieee128_float_type_node): Likewise. + ==================== work097, patch002 Rework 128-bit complex multiply and divide.
next reply other threads:[~2022-08-09 22:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-09 22:32 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 21:06 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=20220809223218.CCE3D385801A@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).