From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 7/7] Delete enum inferior_event_handler::INF_TIMER
Date: Wed, 12 Aug 2015 17:11:00 -0000 [thread overview]
Message-ID: <1439398917-22761-8-git-send-email-palves@redhat.com> (raw)
In-Reply-To: <1439398917-22761-1-git-send-email-palves@redhat.com>
Nothing ever uses this.
gdb/ChangeLog:
2015-08-12 Pedro Alves <palves@redhat.com>
* inf-loop.c (inferior_event_handler): Delete INF_TIMER case.
* target.h (enum inferior_event_type) <INF_TIMER>: Delete.
---
gdb/inf-loop.c | 1 -
gdb/target.h | 2 --
2 files changed, 3 deletions(-)
diff --git a/gdb/inf-loop.c b/gdb/inf-loop.c
index 8aecfe6..aac936f 100644
--- a/gdb/inf-loop.c
+++ b/gdb/inf-loop.c
@@ -80,7 +80,6 @@ inferior_event_handler (enum inferior_event_type event_type,
}
break;
- case INF_TIMER:
default:
printf_unfiltered (_("Event type not recognized.\n"));
break;
diff --git a/gdb/target.h b/gdb/target.h
index dc3a6d6..bc23f9e 100644
--- a/gdb/target.h
+++ b/gdb/target.h
@@ -122,8 +122,6 @@ enum inferior_event_type
/* Process a normal inferior event which will result in target_wait
being called. */
INF_REG_EVENT,
- /* We are called because a timer went off. */
- INF_TIMER,
/* We are called to do stuff after the inferior stops. */
INF_EXEC_COMPLETE,
};
--
1.9.3
next prev parent reply other threads:[~2015-08-12 17:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 17:02 [PATCH 0/7] Replace continuations with an extendable "class" Pedro Alves
2015-08-12 17:02 ` [PATCH 4/7] Convert the until/advance commands to thread_fsm mechanism Pedro Alves
2015-08-12 17:02 ` [PATCH 3/7] Convert infcalls " Pedro Alves
2015-08-12 17:02 ` [PATCH 2/7] Replace "struct continuation" mechanism by something more extensible Pedro Alves
2015-08-18 12:50 ` Yao Qi
2015-08-19 14:55 ` Pedro Alves
2015-08-12 17:02 ` [PATCH 1/7] Merge async and sync code paths some more Pedro Alves
2015-08-12 19:48 ` Simon Marchi
2015-08-17 17:54 ` Pedro Alves
2015-08-17 19:28 ` Simon Marchi
2015-08-18 10:48 ` Yao Qi
2015-08-19 14:11 ` Pedro Alves
2015-08-27 13:26 ` Yao Qi
2015-10-16 0:35 ` Joel Brobecker
2015-10-16 12:24 ` Pedro Alves
2015-10-16 16:22 ` Joel Brobecker
2015-10-16 16:37 ` Pedro Alves
2015-10-16 17:05 ` Joel Brobecker
2015-10-22 16:18 ` Pedro Alves
2015-08-12 17:11 ` [PATCH 6/7] Garbage collect thread continuations Pedro Alves
2015-08-12 17:11 ` [PATCH 5/7] Garbage collect dummy_frame_ctx_saver Pedro Alves
2015-08-12 17:11 ` Pedro Alves [this message]
2015-08-18 11:22 ` [PATCH 7/7] Delete enum inferior_event_handler::INF_TIMER Yao Qi
2015-08-18 12:52 ` [PATCH 0/7] Replace continuations with an extendable "class" Yao Qi
2015-08-19 14:56 ` Pedro Alves
2015-09-09 17:33 ` Pedro Alves
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=1439398917-22761-8-git-send-email-palves@redhat.com \
--to=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).