public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Philipp Tomsich <ptomsich@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/vrull/heads/slp-improvements)] Fix signedness warnings in aarch64_evpc_ins_uzp
Date: Wed, 17 Jan 2024 19:14:36 +0000 (GMT)	[thread overview]
Message-ID: <20240117191436.5E1D13858C66@sourceware.org> (raw)

https://gcc.gnu.org/g:313febe010385fe9dbca0af3611a84cfec650af6

commit 313febe010385fe9dbca0af3611a84cfec650af6
Author: Manolis Tsamis <manolis.tsamis@vrull.eu>
Date:   Fri Nov 24 10:12:53 2023 +0100

    Fix signedness warnings in aarch64_evpc_ins_uzp
    
    Ref #344

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

diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
index 7ae94091b7e..14b9a9d860e 100644
--- a/gcc/config/aarch64/aarch64.cc
+++ b/gcc/config/aarch64/aarch64.cc
@@ -25846,15 +25846,15 @@ aarch64_evpc_ins_uzp (struct expand_vec_perm_d *d)
     return false;
 
   /* We have a {A, B, A, B} permutation.  */
-  HOST_WIDE_INT A = d->perm[0].to_constant ();
-  HOST_WIDE_INT B = d->perm[1].to_constant ();
+  unsigned HOST_WIDE_INT A = d->perm[0].to_constant ();
+  unsigned HOST_WIDE_INT B = d->perm[1].to_constant ();
 
   if (A >= nelt || B < nelt || d->op0 == d->op1)
     return false;
 
   rtx insv;
   rtx extractv;
-  HOST_WIDE_INT idx, extractindex;
+  unsigned HOST_WIDE_INT idx, extractindex;
 
   /* If A is the first element or B is the second element of a UZP1/2 then we
      can emit this permute as INS + UZP .  */

             reply	other threads:[~2024-01-17 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 19:14 Philipp Tomsich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-23 20:57 Philipp Tomsich
2023-11-28 13:35 Philipp Tomsich

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=20240117191436.5E1D13858C66@sourceware.org \
    --to=ptomsich@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).