public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Filip Kastl <pheeck@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/pheeck/heads/sccp)] analyzer: fix Clang warnings
Date: Wed, 15 Feb 2023 10:23:24 +0000 (GMT)	[thread overview]
Message-ID: <20230215102324.2140B3858422@sourceware.org> (raw)

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

commit a30997389ffd51808e04bb527f20ff38a4d6adf1
Author: Martin Liska <mliska@suse.cz>
Date:   Thu Nov 24 08:40:10 2022 +0100

    analyzer: fix Clang warnings
    
    Fixes the following warnings:
    gcc/analyzer/varargs.cc:655:8: warning: 'matches_call_types_p' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
    gcc/analyzer/varargs.cc:707:50: warning: unused parameter 'cd' [-Wunused-parameter]
    gcc/analyzer/varargs.cc:707:8: warning: 'matches_call_types_p' overrides a member function but is not marked 'override' [-Winconsistent-missing-override]
    
    gcc/analyzer/ChangeLog:
    
            * varargs.cc: Fix Clang warnings.

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

diff --git a/gcc/analyzer/varargs.cc b/gcc/analyzer/varargs.cc
index 1da5a46f677..daa937d9c65 100644
--- a/gcc/analyzer/varargs.cc
+++ b/gcc/analyzer/varargs.cc
@@ -652,7 +652,7 @@ make_va_list_state_machine (logger *logger)
 class kf_va_start : public known_function
 {
 public:
-  bool matches_call_types_p (const call_details &) const
+  bool matches_call_types_p (const call_details &) const final override
   {
     return true;
   }
@@ -704,7 +704,7 @@ kf_va_start::impl_call_pre (const call_details &cd) const
 class kf_va_copy : public known_function
 {
 public:
-  bool matches_call_types_p (const call_details &cd) const
+  bool matches_call_types_p (const call_details &) const final override
   {
     return true;
   }

                 reply	other threads:[~2023-02-15 10:23 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=20230215102324.2140B3858422@sourceware.org \
    --to=pheeck@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).