public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-230] recog.cc: Correct comments referring to parameter match_len
Date: Tue, 25 Apr 2023 23:12:51 +0000 (GMT)	[thread overview]
Message-ID: <20230425231251.E3D023858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:064eed39d232b0984a0199a6163e3db68e41671f

commit r14-230-g064eed39d232b0984a0199a6163e3db68e41671f
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Wed Apr 19 17:45:57 2023 +0200

    recog.cc: Correct comments referring to parameter match_len
    
            * recog.cc (peep2_attempt, peep2_update_life): Correct
            head-comment description of parameter match_len.

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

diff --git a/gcc/recog.cc b/gcc/recog.cc
index 3ddeab59d92..fd09145d45e 100644
--- a/gcc/recog.cc
+++ b/gcc/recog.cc
@@ -3850,7 +3850,7 @@ copy_frame_info_to_split_insn (rtx_insn *old_insn, rtx_insn *new_insn)
   maybe_copy_prologue_epilogue_insn (old_insn, new_insn);
 }
 
-/* While scanning basic block BB, we found a match of length MATCH_LEN,
+/* While scanning basic block BB, we found a match of length MATCH_LEN + 1,
    starting at INSN.  Perform the replacement, removing the old insns and
    replacing them with ATTEMPT.  Returns the last insn emitted, or NULL
    if the replacement is rejected.  */
@@ -4036,7 +4036,7 @@ peep2_attempt (basic_block bb, rtx_insn *insn, int match_len, rtx_insn *attempt)
 /* After performing a replacement in basic block BB, fix up the life
    information in our buffer.  LAST is the last of the insns that we
    emitted as a replacement.  PREV is the insn before the start of
-   the replacement.  MATCH_LEN is the number of instructions that were
+   the replacement.  MATCH_LEN + 1 is the number of instructions that were
    matched, and which now need to be replaced in the buffer.  */
 
 static void

                 reply	other threads:[~2023-04-25 23:12 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=20230425231251.E3D023858D28@sourceware.org \
    --to=hp@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).