public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tamar Christina <tnfchris@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4122] middle-end: replace GET_MODE_WIDER_MODE with GET_MODE_NEXT_MODE
Date: Thu, 17 Nov 2022 08:22:02 +0000 (GMT)	[thread overview]
Message-ID: <20221117082202.A59E2385188E@sourceware.org> (raw)

https://gcc.gnu.org/g:1bc7efa948f75131aa29d5a2337641c4e39fc7c6

commit r13-4122-g1bc7efa948f75131aa29d5a2337641c4e39fc7c6
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Thu Nov 17 08:14:44 2022 +0000

    middle-end: replace GET_MODE_WIDER_MODE with GET_MODE_NEXT_MODE
    
    After the fix to the addsub patch yesterday for bootstrap I had only regtested on x86.
    While looking today it seemed the new tests were failing, this was caused
    by a change in the behavior of the GET_MODE_WIDER_MODE macro on trunk.
    
    gcc/ChangeLog:
    
            * match.pd: Replace GET_MODE_WIDER_MODE with
            custom code.

Diff:
---
 gcc/match.pd | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/gcc/match.pd b/gcc/match.pd
index 39edc894aa5..fe1178cf0d5 100644
--- a/gcc/match.pd
+++ b/gcc/match.pd
@@ -7940,12 +7940,15 @@ and,
        vec_perm_indices sel (builder, 2, nelts);
        machine_mode vec_mode = TYPE_MODE (type);
        machine_mode wide_mode;
+       scalar_mode wide_elt_mode;
+       poly_uint64 wide_nunits;
+       scalar_mode inner_mode = GET_MODE_INNER (vec_mode);
      }
      (if (sel.series_p (0, 2, 0, 2)
-          && GET_MODE_WIDER_MODE (vec_mode).exists (&wide_mode)
-	  && VECTOR_MODE_P (wide_mode)
-	  && (GET_MODE_UNIT_BITSIZE (vec_mode) * 2
-	      == GET_MODE_UNIT_BITSIZE (wide_mode)))
+	  && GET_MODE_2XWIDER_MODE (inner_mode).exists (&wide_elt_mode)
+	  && multiple_p (GET_MODE_NUNITS (vec_mode), 2, &wide_nunits)
+	  && related_vector_mode (vec_mode, wide_elt_mode,
+				  wide_nunits).exists (&wide_mode))
 	(with
 	 {
 	   tree stype

                 reply	other threads:[~2022-11-17  8:22 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=20221117082202.A59E2385188E@sourceware.org \
    --to=tnfchris@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).