From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][pushed] analyzer: add more final override keywords
Date: Tue, 16 Aug 2022 11:01:01 +0200 [thread overview]
Message-ID: <b0322e4c-bba1-42f4-2c5e-49f700191169@suse.cz> (raw)
Pushed as obvious.
Martin
gcc/analyzer/ChangeLog:
* region-model.cc: Fix -Winconsistent-missing-override clang
warning.
* region.h: Likewise.
---
gcc/analyzer/region-model.cc | 4 ++--
gcc/analyzer/region.h | 3 ++-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/gcc/analyzer/region-model.cc b/gcc/analyzer/region-model.cc
index b05b7097c00..b5bc3efda32 100644
--- a/gcc/analyzer/region-model.cc
+++ b/gcc/analyzer/region-model.cc
@@ -3425,7 +3425,7 @@ public:
result_set.add (sval);
}
- void visit_unaryop_svalue (const unaryop_svalue *sval)
+ void visit_unaryop_svalue (const unaryop_svalue *sval) final override
{
const svalue *arg = sval->get_arg ();
if (result_set.contains (arg))
@@ -3449,7 +3449,7 @@ public:
}
}
- void visit_repeated_svalue (const repeated_svalue *sval)
+ void visit_repeated_svalue (const repeated_svalue *sval) final override
{
sval->get_inner_svalue ()->accept (this);
if (result_set.contains (sval->get_inner_svalue ()))
diff --git a/gcc/analyzer/region.h b/gcc/analyzer/region.h
index 20dffc7f577..d37584b7285 100644
--- a/gcc/analyzer/region.h
+++ b/gcc/analyzer/region.h
@@ -919,7 +919,8 @@ public:
const svalue *get_byte_offset () const { return m_byte_offset; }
bool get_relative_concrete_offset (bit_offset_t *out) const final override;
- const svalue * get_byte_size_sval (region_model_manager *mgr) const;
+ const svalue * get_byte_size_sval (region_model_manager *mgr)
+ const final override;
private:
--
2.37.1
reply other threads:[~2022-08-16 9:01 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=b0322e4c-bba1-42f4-2c5e-49f700191169@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@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).