From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] cleanup infrun.c:handle_inferior_event some more.
Date: Wed, 23 Oct 2013 20:07:00 -0000 [thread overview]
Message-ID: <1382558820-28691-1-git-send-email-palves@redhat.com> (raw)
Here are some more cleanups to handle_inferior_event, while I'm
looking at it. It ends up breaking handle_inferior_event in two
halves plus one smaller piece. handle_inferior_event ends up a bit
over half of its current size (~2100 -> ~1200 lines), which I think
everyone will agree is better than the status quo.
Tested on x86_64 Fedora 17.
Pedro Alves (5):
infrun.c:handle_inferior_event: Remove some more dead code.
infrun.c:handle_inferior_event: Put all ecs->random_signal tests
together.
infrun.c:handle_inferior_event: Move process_event_stop_test goto
label.
infrun.c:handle_inferior_event: Make process_event_stop_test label a
function.
infrun.c:process_event_stop_test: Reindent.
gdb/infrun.c | 585 ++++++++++++++++++++++++++++++-----------------------------
1 file changed, 297 insertions(+), 288 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-10-23 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 20:07 Pedro Alves [this message]
2013-10-23 20:07 ` [PATCH 1/5] infrun.c:handle_inferior_event: Remove some more dead code Pedro Alves
2013-10-24 15:58 ` Gary Benson
2013-10-23 20:34 ` [PATCH 2/5] infrun.c:handle_inferior_event: Put all ecs->random_signal tests together Pedro Alves
2013-10-23 20:34 ` [PATCH 5/5] infrun.c:process_event_stop_test: Reindent Pedro Alves
2013-10-23 20:34 ` [PATCH 4/5] infrun.c:handle_inferior_event: Make process_event_stop_test label a function Pedro Alves
2013-10-23 20:34 ` [PATCH 3/5] infrun.c:handle_inferior_event: Move process_event_stop_test goto label Pedro Alves
2013-10-28 19:35 ` [PATCH 0/5] cleanup infrun.c:handle_inferior_event some more 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=1382558820-28691-1-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).