public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/meissner/heads/dmf004)] Fix lxvl and stxvl wrong conditional branch.
Date: Thu, 17 Nov 2022 21:55:51 +0000 (GMT)	[thread overview]
Message-ID: <20221117215551.59BB2384F6C6@sourceware.org> (raw)

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

commit e9c3f7a87eab783efd9356b0214aadcd7fa00d2e
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Nov 17 00:14:06 2022 -0500

    Fix lxvl and stxvl wrong conditional branch.
    
    2022-11-16   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
    
            * config/rs6000/rs6000-string.cc (expand_block_move_variable): Fix wrong
            conditional branch.

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

diff --git a/gcc/config/rs6000/rs6000-string.cc b/gcc/config/rs6000/rs6000-string.cc
index 216c0c1cc93..ee17ddb87e1 100644
--- a/gcc/config/rs6000/rs6000-string.cc
+++ b/gcc/config/rs6000/rs6000-string.cc
@@ -2844,7 +2844,7 @@ expand_block_move_variable (rtx operands[], bool might_overlap)
 			      gen_rtx_COMPARE (CCmode, bytes_rtx,
 					       const0_rtx)));
 
-      do_ifelse (CCmode, GT, NULL_RTX, NULL_RTX, vect_cr, join_label,
+      do_ifelse (CCmode, LE, NULL_RTX, NULL_RTX, vect_cr, join_label,
 		 profile_probability::likely ());
 
       rtx ptr_adjust = GEN_INT (vect_size_int);

             reply	other threads:[~2022-11-17 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 21:55 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-17  5:14 Michael Meissner

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=20221117215551.59BB2384F6C6@sourceware.org \
    --to=meissner@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).