public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112993] rs6000: Rework precision for 128bit float types and modes
Date: Wed, 17 Jul 2024 05:21:27 +0000	[thread overview]
Message-ID: <bug-112993-4-ZSUyZ2hxVZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112993-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112993

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:b5c813ed6035cf6ef831927e66e184a5847afbe6

commit r15-2087-gb5c813ed6035cf6ef831927e66e184a5847afbe6
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Jul 17 00:19:00 2024 -0500

    tree: Remove KFmode workaround [PR112993]

    The fix for PR112993 makes KFmode have 128 bit mode precision,
    we don't need this workaround to fix up the type precision any
    more, and just go with mode precision.  So this patch is to
    remove KFmode workaround.

            PR target/112993

    gcc/ChangeLog:

            * tree.cc (build_common_tree_nodes): Drop the workaround for rs6000
            KFmode precision adjustment.

  parent reply	other threads:[~2024-07-17  5:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13  2:15 [Bug target/112993] New: " linkw at gcc dot gnu.org
2023-12-13  2:17 ` [Bug target/112993] " linkw at gcc dot gnu.org
2023-12-13  2:43 ` linkw at gcc dot gnu.org
2024-07-17  5:21 ` cvs-commit at gcc dot gnu.org
2024-07-17  5:21 ` cvs-commit at gcc dot gnu.org
2024-07-17  5:21 ` cvs-commit at gcc dot gnu.org
2024-07-17  5:21 ` cvs-commit at gcc dot gnu.org
2024-07-17  5:21 ` cvs-commit at gcc dot gnu.org [this message]
2024-07-17  5:28 ` linkw at gcc dot gnu.org
2024-08-14  3:20 ` linkw at gcc dot gnu.org

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=bug-112993-4-ZSUyZ2hxVZ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).