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)] Make __float128 use the _Float128 type. Date: Fri, 12 Aug 2022 01:11:50 +0000 (GMT) [thread overview] Message-ID: <20220812011150.137F93858D28@sourceware.org> (raw) https://gcc.gnu.org/g:5781bb7754809e81cbb661c891b28c6d2a1f1432 commit 5781bb7754809e81cbb661c891b28c6d2a1f1432 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Aug 11 21:11:26 2022 -0400 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. Diff: --- gcc/config/rs6000/rs6000-builtin.cc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/gcc/config/rs6000/rs6000-builtin.cc b/gcc/config/rs6000/rs6000-builtin.cc index e34a8f0cebf..1cc97fa49b3 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) { - if (TARGET_IEEEQUAD && TARGET_LONG_DOUBLE_128) - ieee128_float_type_node = long_double_type_node; - else - ieee128_float_type_node = float128_type_node; + /* 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; 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 1:11 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-12 1:11 Michael Meissner [this message] 2022-08-12 4:17 Michael Meissner 2022-08-12 20:54 Michael Meissner 2022-08-12 21:01 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=20220812011150.137F93858D28@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).