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/work107)] Update ChangeLog.meissner Date: Wed, 25 Jan 2023 03:00:56 +0000 (GMT) [thread overview] Message-ID: <20230125030056.385563858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:7a745792382b35c9efcd07a2baf53938235c4c30 commit 7a745792382b35c9efcd07a2baf53938235c4c30 Author: Michael Meissner <meissner@linux.ibm.com> Date: Tue Jan 24 22:00:53 2023 -0500 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 2479292e9e8..182a2e87e0d 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,34 @@ +==================== work107, patch #20 ==================== + +Improve PowerPC 128-bit floating point types. + +This patch prevents __ibm128 and __float128 from being considered in the +automatic widening that the compiler does. This way, you don't have the +possibility that IFmode (__ibm128) will be widened to TFmode or KFmode, even +there is hardware to support the IEEE 128-bit operations. + +I also moved changing the TFmode format from ieee to ibm to rs6000-modes.def +from rs6000.cc. + +2022-01-24 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000-modes.def (IFmode): Rework to use + FRACTIONAL_FLOAT_MODE_NO_WIDEN. + (KFmode): Likewise. + * expr.cc (convert_mode_scalar): Don't abort if we are converting + floating point modes that are the same precision but use different + encodings. + * genmodes.cc (struct mode_data): Add support for no widening. + (blank_mode): Likewise. + (FRACTIONAL_FLOAT_MODE): Add support for no widening capability. + (FRACTIONAL_FLOAT_MODE_NO_WIDEN): New macro. + (make_float_mode): Add support for no widening capability. + (cmp_modes): Likewise. + (emit_mode_wider): Add support for no widening capability. + * machmode.def (FRACTIONAL_FLOAT_MODE_NO_WIDEN): Document. + ==================== work107, rebase 1/23 ==================== ==================== work107, patch #2 ====================
next reply other threads:[~2023-01-25 3:00 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-25 3:00 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-25 4:42 Michael Meissner 2023-01-25 3:29 Michael Meissner 2023-01-23 21:19 Michael Meissner 2023-01-23 21:17 Michael Meissner 2023-01-23 21:17 Michael Meissner 2023-01-20 21:02 Michael Meissner 2023-01-20 20:34 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=20230125030056.385563858D1E@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).