Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH OBV] Remove any_running
Date: Thu, 19 Jun 2014 05:52:00 -0000	[thread overview]
Message-ID: <1403157035-13558-1-git-send-email-yao@codesourcery.com> (raw)

Function any_running isn't used.  This patch is to remove it.
Rebuild GDB for linux and mingw.

gdb:

2014-06-19  Yao Qi  <yao@codesourcery.com>

	* gdbthread.h (any_running): Remove the declaration.
	* thread.c (any_running): Remove.
---
 gdb/gdbthread.h |  3 ---
 gdb/thread.c    | 12 ------------
 2 files changed, 15 deletions(-)

diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h
index 1f10469..689fe9e 100644
--- a/gdb/gdbthread.h
+++ b/gdb/gdbthread.h
@@ -361,9 +361,6 @@ extern int is_exited (ptid_t ptid);
 /* In the frontend's perpective, is this thread stopped?  */
 extern int is_stopped (ptid_t ptid);
 
-/* In the frontend's perpective is there any thread running?  */
-extern int any_running (void);
-
 /* Marks thread PTID as executing, or not.  If ptid_get_pid (PTID) is -1,
    marks all threads.
 
diff --git a/gdb/thread.c b/gdb/thread.c
index 7bc5271..0c40b80 100644
--- a/gdb/thread.c
+++ b/gdb/thread.c
@@ -648,18 +648,6 @@ is_running (ptid_t ptid)
 }
 
 int
-any_running (void)
-{
-  struct thread_info *tp;
-
-  for (tp = thread_list; tp; tp = tp->next)
-    if (tp->state == THREAD_RUNNING)
-      return 1;
-
-  return 0;
-}
-
-int
 is_executing (ptid_t ptid)
 {
   struct thread_info *tp;
-- 
1.9.0


             reply	other threads:[~2014-06-19  5:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  5:52 Yao Qi [this message]
2014-07-10 18:18 ` Doug Evans
2014-07-10 19:14   ` Tom Tromey
2014-07-10 19:21     ` Doug Evans
2014-07-10 19:35       ` Tom Tromey
2014-07-14 19:13         ` Doug Evans

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=1403157035-13558-1-git-send-email-yao@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@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