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/work093)] Update ChangeLog.meissner. Date: Thu, 30 Jun 2022 06:01:42 +0000 (GMT) [thread overview] Message-ID: <20220630060142.C3610384D1BC@sourceware.org> (raw) https://gcc.gnu.org/g:de859c383f48df4cb9460d150f415b792649db84 commit de859c383f48df4cb9460d150f415b792649db84 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Jun 30 02:01:24 2022 -0400 Update ChangeLog.meissner. 2022-06-30 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index e18fd3a4518..d9171216954 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,43 @@ +==================== work093, patch #2 + +Add support to built-ins for long double using IEEE 128-bit. + +This patch lays the ground work that future patches will use to add +builtin support (both normal and overloaded) for the case where long +double uses the IEEE 128-bit encoding. The issue to enable migrating the +builtins to use the overload facility to allow both __float128 and long +double to the functions. + +This adds a new stanza (ieee128-hw-ld) for when we have IEEE 128-bit +hardware support and long double uses the IEEE 128-bit encoding. + +A new type attribute (ieeeld) is added for long double if long double uses +the IEEE 128-bit encoding. + +2022-06-30 Michael Meissner <meissner@linux.ibm.com> + + +gcc/ + + * config/rs6000/rs6000-builtin.cc (rs6000_invalid_builtin): Add + support for ibm128-hw-ld stanza. + (rs6000_builtin_is_supported): Likewise. + (rs6000_init_builtins): Likewise. + (rs6000_expand_builtin): Add support for IEEE128_HW_LD. Add + support for ieeeld. + * config/rs6000/rs6000-builtins.def (toplevel): Add comment about + the new ieeeld attribute. + * config/rs6000/rs6000-gen-builtins.cc (enum bif_stanza): Add + BSTZ_IEEE128_HW_LD. + (stanza_map): Likewise. + (enable_string): Likewise. + (attrinfo): Add isieeeld. + (parse_bif_attrs): Parse ieeeld. Add printing ieeeld to the debug + print. + (write_decls): Add support for ibm128-hw-ld stanza and ieeeld + attribute. + (write_bif_static_init): Add support for ieeeld attribute. + ==================== work093, patch #1 Change __ieee128 to __float128.
next reply other threads:[~2022-06-30 6:01 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-30 6:01 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-07-12 2:52 Michael Meissner 2022-07-12 1:37 Michael Meissner 2022-07-08 20:02 Michael Meissner 2022-07-08 2:27 Michael Meissner 2022-07-07 23:39 Michael Meissner 2022-07-07 21:08 Michael Meissner 2022-07-07 20:22 Michael Meissner 2022-07-07 16:32 Michael Meissner 2022-07-07 4:40 Michael Meissner 2022-07-06 22:15 Michael Meissner 2022-07-06 21:15 Michael Meissner 2022-07-01 7:26 Michael Meissner 2022-07-01 6:48 Michael Meissner 2022-06-30 20:28 Michael Meissner 2022-06-30 19:22 Michael Meissner 2022-06-30 19:18 Michael Meissner 2022-06-30 17:43 Michael Meissner 2022-06-30 15:22 Michael Meissner 2022-06-30 4:30 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=20220630060142.C3610384D1BC@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).