public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-6954] Fix comment for operand_compare::operand_equal_p.
Date: Mon, 31 Jan 2022 23:26:43 +0000 (GMT)	[thread overview]
Message-ID: <20220131232643.4A5703857C50@sourceware.org> (raw)

https://gcc.gnu.org/g:691924db0d85f2e6851f0a633ba4e2d6b874b772

commit r12-6954-g691924db0d85f2e6851f0a633ba4e2d6b874b772
Author: Andrew Pinski <apinski@marvell.com>
Date:   Thu Jan 27 01:22:48 2022 +0000

    Fix comment for operand_compare::operand_equal_p.
    
    The OEP_* enums were moved to tree-core.h in
    r0-124973-g5e351e960763 but the comment was correct
    when it was added added to fold-const.h in
    r10-4231-g7f4a8ee03d40. This fixes the reference
    to the OEP_* enum to reference tree-core.
    
    Committed as obvious after a bootstrap/test on x86_64-linux.
    
    gcc/ChangeLog:
    
            * fold-const.h (operand_compare::operand_equal_p):
            Fix comment about OEP_* flags.

Diff:
---
 gcc/fold-const.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/fold-const.h b/gcc/fold-const.h
index a9a3062e4f6..394a67ece79 100644
--- a/gcc/fold-const.h
+++ b/gcc/fold-const.h
@@ -243,7 +243,7 @@ class operand_compare
 {
 public:
   /* Return true if two operands are equal.  The flags fields can be used
-     to specify OEP flags described above.  */
+     to specify OEP flags described in tree-core.h.  */
   virtual bool operand_equal_p (const_tree, const_tree, unsigned int flags);
 
   /* Generate a hash value for an expression.  This can be used iteratively


                 reply	other threads:[~2022-01-31 23:26 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=20220131232643.4A5703857C50@sourceware.org \
    --to=pinskia@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).