public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] analyzer: fix stray get_element decls
Date: Thu, 28 Jul 2022 12:10:02 +0000 (GMT)	[thread overview]
Message-ID: <20220728121002.E3F2A385AE53@sourceware.org> (raw)

https://gcc.gnu.org/g:4b15027355e4bd4349b0f8d6a338647a4e3cc48b

commit 4b15027355e4bd4349b0f8d6a338647a4e3cc48b
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Tue Jul 26 14:43:59 2022 -0400

    analyzer: fix stray get_element decls
    
    These were copy&paste errors.
    
    gcc/analyzer/ChangeLog:
            * region.h (code_region::get_element): Remove stray decl.
            (function_region::get_element): Likewise.
    
    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

Diff:
---
 gcc/analyzer/region.h | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/gcc/analyzer/region.h b/gcc/analyzer/region.h
index fd0d4a05cc9..1067748a7cd 100644
--- a/gcc/analyzer/region.h
+++ b/gcc/analyzer/region.h
@@ -400,10 +400,6 @@ public:
   /* region vfuncs.  */
   void dump_to_pp (pretty_printer *pp, bool simple) const final override;
   enum region_kind get_kind () const final override { return RK_CODE; }
-
-  const region *get_element (region_model *model,
-			const svalue *index,
-			region_model_context *ctxt);
 };
 
 } // namespace ana
@@ -439,10 +435,6 @@ public:
 
   tree get_fndecl () const { return m_fndecl; }
 
-  region *get_element (region_model *model,
-			const svalue *index_sid,
-			region_model_context *ctxt);
-
 private:
   tree m_fndecl;
 };


                 reply	other threads:[~2022-07-28 12:10 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=20220728121002.E3F2A385AE53@sourceware.org \
    --to=marxin@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).