public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: jeevitha <jeevitha@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-7426] rs6000: Remove duplicate expression [PR106907]
Date: Wed,  7 Jun 2023 16:28:58 +0000 (GMT)	[thread overview]
Message-ID: <20230607162858.EE1E03858C54@sourceware.org> (raw)

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

commit r13-7426-gdda4745eb1c9b063c6004baef54aa4cec97edf3d
Author: Jeevitha Palanisamy <jeevitha@linux.ibm.com>
Date:   Tue Jun 6 06:19:02 2023 -0500

    rs6000: Remove duplicate expression [PR106907]
    
    PR106907 has few warnings spotted from cppcheck. In that addressing duplicate
    expression issue here. Here the same expression is used twice in logical
    AND(&&) operation which result in same result so removing that.
    
    2023-06-06  Jeevitha Palanisamy  <jeevitha@linux.ibm.com>
    
    gcc/
            PR target/106907
            * config/rs6000/rs6000.cc (vec_const_128bit_to_bytes): Remove
            duplicate expression.
    
    (cherry picked from commit c4deccd44655c5d748dfed200a37f2b678c32fe8)

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

diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc
index 6debf0f63ff..45702d86588 100644
--- a/gcc/config/rs6000/rs6000.cc
+++ b/gcc/config/rs6000/rs6000.cc
@@ -28762,7 +28762,6 @@ vec_const_128bit_to_bytes (rtx op,
 
   info->all_words_same
     = (info->words[0] == info->words[1]
-       && info->words[0] == info->words[1]
        && info->words[0] == info->words[2]
        && info->words[0] == info->words[3]);

                 reply	other threads:[~2023-06-07 16:28 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=20230607162858.EE1E03858C54@sourceware.org \
    --to=jeevitha@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).