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, 7 Jul 2022 04:40:18 +0000 (GMT) [thread overview] Message-ID: <20220707044018.EE1E43858D32@sourceware.org> (raw) https://gcc.gnu.org/g:005abb905e1a752a4c35a5fb40d9b12f70240284 commit 005abb905e1a752a4c35a5fb40d9b12f70240284 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Jul 7 00:40:01 2022 -0400 Update ChangeLog.meissner. 2022-07-07 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index cb09858dc95..bbbe2f43834 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,17 @@ +==================== work093, patch #8 + +Fixup KFmode to TFmode built-in functions. + +2022-07-07 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000-builtin.cc (rs6000_expand_builtin): If we + have certain KFmode built-in functions, convert to TFmode if a + long double was passed, and long double is IEEE 128-bit. Also if + the modes are different, call convert_to_mode instead of + copy_to_mode_reg. + ==================== work093, patch #7 __float128 and __ibm128 always gets different internal types.
next reply other threads:[~2022-07-07 4:40 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-07 4:40 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-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 6:01 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=20220707044018.EE1E43858D32@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).