public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Prathamesh Kulkarni <prathamesh3492@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-1701] [aarch64] Use op_mode instead of vmode in aarch64_vectorize_vec_perm_const.
Date: Fri, 15 Jul 2022 01:01:47 +0000 (GMT)	[thread overview]
Message-ID: <20220715010147.16E4C3857B8A@sourceware.org> (raw)

https://gcc.gnu.org/g:4cbebddc2ce1e88216fec6aa89d111d8596bd34c

commit r13-1701-g4cbebddc2ce1e88216fec6aa89d111d8596bd34c
Author: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
Date:   Fri Jul 15 06:26:50 2022 +0530

    [aarch64] Use op_mode instead of vmode in aarch64_vectorize_vec_perm_const.
    
    gcc/ChangeLog:
            * config/aarch64/aarch64.cc (aarch64_vectorize_vec_perm_const): Use
            op_mode instead of vmode in calls to force_reg for op0 and op1.

Diff:
---
 gcc/config/aarch64/aarch64.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
index 25f4cbb466d..303814b8cca 100644
--- a/gcc/config/aarch64/aarch64.cc
+++ b/gcc/config/aarch64/aarch64.cc
@@ -24129,11 +24129,11 @@ aarch64_vectorize_vec_perm_const (machine_mode vmode, machine_mode op_mode,
   d.op_mode = op_mode;
   d.op_vec_flags = aarch64_classify_vector_mode (d.op_mode);
   d.target = target;
-  d.op0 = op0 ? force_reg (vmode, op0) : NULL_RTX;
+  d.op0 = op0 ? force_reg (op_mode, op0) : NULL_RTX;
   if (op0 == op1)
     d.op1 = d.op0;
   else
-    d.op1 = op1 ? force_reg (vmode, op1) : NULL_RTX;
+    d.op1 = op1 ? force_reg (op_mode, op1) : NULL_RTX;
   d.testing_p = !target;
 
   if (!d.testing_p)


                 reply	other threads:[~2022-07-15  1:01 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=20220715010147.16E4C3857B8A@sourceware.org \
    --to=prathamesh3492@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).