public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Arthur Cohen <cohenarthur@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-8112] gccrs: Add missing override specifier
Date: Tue, 16 Jan 2024 18:19:41 +0000 (GMT)	[thread overview]
Message-ID: <20240116181941.30125385DC35@sourceware.org> (raw)

https://gcc.gnu.org/g:74ef5529c81fc3ad4bcb873ceba045f8142ddcfe

commit r14-8112-g74ef5529c81fc3ad4bcb873ceba045f8142ddcfe
Author: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>
Date:   Thu Nov 2 18:10:32 2023 +0100

    gccrs: Add missing override specifier
    
    Some function lacked the override specifier, this made the compiler emit
    several warning.
    
    gcc/rust/ChangeLog:
    
            * ast/rust-ast.h: Add override specifier.
            * ast/rust-item.h: Likewise.
    
    Signed-off-by: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>

Diff:
---
 gcc/rust/ast/rust-ast.h  | 2 +-
 gcc/rust/ast/rust-item.h | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/rust/ast/rust-ast.h b/gcc/rust/ast/rust-ast.h
index 9f5242ae80d..75af2940c76 100644
--- a/gcc/rust/ast/rust-ast.h
+++ b/gcc/rust/ast/rust-ast.h
@@ -1495,7 +1495,7 @@ public:
   }
 
   NodeId get_node_id () const { return node_id; }
-  location_t get_locus () const { return locus; }
+  location_t get_locus () const override { return locus; }
 };
 
 /* Abstract base class for items used within an inherent impl block (the impl
diff --git a/gcc/rust/ast/rust-item.h b/gcc/rust/ast/rust-item.h
index eba86dca2fa..57059eb0672 100644
--- a/gcc/rust/ast/rust-item.h
+++ b/gcc/rust/ast/rust-item.h
@@ -3291,7 +3291,7 @@ public:
 
   std::string as_string () const override;
 
-  location_t get_locus () const { return locus; }
+  location_t get_locus () const override { return locus; }
 
   void accept_vis (ASTVisitor &vis) override;

                 reply	other threads:[~2024-01-16 18:19 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=20240116181941.30125385DC35@sourceware.org \
    --to=cohenarthur@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).