public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Remove windows_thread_info destructor
Date: Mon,  4 Apr 2022 19:59:16 +0000 (GMT)	[thread overview]
Message-ID: <20220404195916.887D43858009@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fc0b013e44e5a450631706bc25612b975cfbc692

commit fc0b013e44e5a450631706bc25612b975cfbc692
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Mar 31 10:58:55 2022 -0600

    Remove windows_thread_info destructor
    
    windows_thread_info declares and defines a destructor, but this
    doesn't need to be explicit.

Diff:
---
 gdb/nat/windows-nat.c | 4 ----
 gdb/nat/windows-nat.h | 2 --
 2 files changed, 6 deletions(-)

diff --git a/gdb/nat/windows-nat.c b/gdb/nat/windows-nat.c
index 21445f3f859..3907286de96 100644
--- a/gdb/nat/windows-nat.c
+++ b/gdb/nat/windows-nat.c
@@ -74,10 +74,6 @@ GenerateConsoleCtrlEvent_ftype *GenerateConsoleCtrlEvent;
   debug_prefixed_printf_cond (debug_events, "windows events", fmt, \
 			      ## __VA_ARGS__)
 
-windows_thread_info::~windows_thread_info ()
-{
-}
-
 void
 windows_thread_info::suspend ()
 {
diff --git a/gdb/nat/windows-nat.h b/gdb/nat/windows-nat.h
index f0abd7d795c..bfb359efbf1 100644
--- a/gdb/nat/windows-nat.h
+++ b/gdb/nat/windows-nat.h
@@ -43,8 +43,6 @@ struct windows_thread_info
   {
   }
 
-  ~windows_thread_info ();
-
   DISABLE_COPY_AND_ASSIGN (windows_thread_info);
 
   /* Ensure that this thread has been suspended.  */


                 reply	other threads:[~2022-04-04 19:59 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=20220404195916.887D43858009@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=gdb-cvs@sourceware.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).