public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r15-704] rs6000: Clean up TF and TD check with FLOAT128_2REG_P
Date: Tue, 21 May 2024 02:02:57 +0000 (GMT)	[thread overview]
Message-ID: <20240521020258.30D4B3858D35@sourceware.org> (raw)

https://gcc.gnu.org/g:2eb1dff8b34a8a7da02b988878172d1b8f203d96

commit r15-704-g2eb1dff8b34a8a7da02b988878172d1b8f203d96
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Mon May 20 21:01:06 2024 -0500

    rs6000: Clean up TF and TD check with FLOAT128_2REG_P
    
    Commit r6-2116-g2c83faf86827bf did some clean up on TFmode
    and TFmode check with FLOAT128_2REG_P, but it missed to
    update an assertion, this patch is to make it align.
    
    btw, it's noticed when I'm making a patch to get rid of
    TFmode.
    
    gcc/ChangeLog:
    
            * config/rs6000/rs6000-call.cc (rs6000_darwin64_record_arg_recurse):
            Clean up TFmode and TDmode check with FLOAT128_2REG_P.

Diff:
---
 gcc/config/rs6000/rs6000-call.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/rs6000/rs6000-call.cc b/gcc/config/rs6000/rs6000-call.cc
index 1f8f93a2ee78..a039ff75f3c9 100644
--- a/gcc/config/rs6000/rs6000-call.cc
+++ b/gcc/config/rs6000/rs6000-call.cc
@@ -1391,7 +1391,7 @@ rs6000_darwin64_record_arg_recurse (CUMULATIVE_ARGS *cum, const_tree type,
 	    if (cum->fregno + n_fpreg > FP_ARG_MAX_REG + 1)
 	      {
 		gcc_assert (cum->fregno == FP_ARG_MAX_REG
-			    && (mode == TFmode || mode == TDmode));
+			    && FLOAT128_2REG_P (mode));
 		/* Long double or _Decimal128 split over regs and memory.  */
 		mode = DECIMAL_FLOAT_MODE_P (mode) ? DDmode : DFmode;
 		cum->use_stack=1;

                 reply	other threads:[~2024-05-21  2:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240521020258.30D4B3858D35@sourceware.org \
    --to=linkw@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: 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).