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)] Revert patch. Date: Fri, 12 Aug 2022 02:39:47 +0000 (GMT) [thread overview] Message-ID: <20220812023947.6EC793858D28@sourceware.org> (raw) https://gcc.gnu.org/g:3dfe6754647f527dbe49bdbc1e34c065276ad537 commit 3dfe6754647f527dbe49bdbc1e34c065276ad537 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Aug 11 22:39:09 2022 -0400 Revert patch. 2022-08-11 Michael Meissner <meissner@linux.ibm.com> gcc/ Revert patches. * config/rs6000/rs6000-builtin.cc (rs6000_init_builtins): Always use the _Float128 type for __float128. Don't use the long double type. * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 11 +---------- gcc/config/rs6000/rs6000-builtin.cc | 8 ++++---- 2 files changed, 5 insertions(+), 14 deletions(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 2e6a3764991..4ae59e38377 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,13 +1,4 @@ -==================== work097, patch008 - -Make __float128 use the _Float128 type. - -2022-08-11 Michael Meissner <meissner@linux.ibm.com> - -gcc/ - - * config/rs6000/rs6000-builtin.cc (rs6000_init_builtins): Always use the - _Float128 type for __float128. Don't use the long double type. +==================== work097, patch008 was reverted ==================== work097, patch007 diff --git a/gcc/config/rs6000/rs6000-builtin.cc b/gcc/config/rs6000/rs6000-builtin.cc index 1cc97fa49b3..e34a8f0cebf 100644 --- a/gcc/config/rs6000/rs6000-builtin.cc +++ b/gcc/config/rs6000/rs6000-builtin.cc @@ -733,10 +733,10 @@ rs6000_init_builtins (void) if (TARGET_FLOAT128_TYPE) { - /* Always make the type used by __float128 to be the same as the - _Float128 type. The C23 standard will want long double to be a - different type than _Float128, so don't use the long double type. */ - ieee128_float_type_node = float128_type_node; + if (TARGET_IEEEQUAD && TARGET_LONG_DOUBLE_128) + ieee128_float_type_node = long_double_type_node; + else + ieee128_float_type_node = float128_type_node; t = build_qualified_type (ieee128_float_type_node, TYPE_QUAL_CONST); lang_hooks.types.register_builtin_type (ieee128_float_type_node, "__ieee128");
next reply other threads:[~2022-08-12 2:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-12 2:39 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-08-12 20:56 Michael Meissner 2022-08-10 18:45 Michael Meissner 2022-08-10 17:24 Michael Meissner 2022-08-10 5:33 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=20220812023947.6EC793858D28@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).