public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] remote.c: Cleanup unused variables
Date: Mon, 08 Feb 2016 18:12:00 -0000 [thread overview]
Message-ID: <5488790363bf8f338e7aec4731f8bed472a2fcf9@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 5488790363bf8f338e7aec4731f8bed472a2fcf9 ***
Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 5488790363bf8f338e7aec4731f8bed472a2fcf9
remote.c: Cleanup unused variables
I built remote.c with -Wunused, to check a function I was working on,
turns out there is a bunch of unused variables.
gdb/ChangeLog:
* remote.c (remote_register_number_and_offset): Remove unused
variable(s).
(remote_thread_always_alive): Likewise.
(remote_update_thread_list): Likewise.
(process_initial_stop_replies): Likewise.
(remote_start_remote): Likewise.
(remote_check_symbols): Likewise.
(discard_pending_stop_replies): Likewise.
(process_stop_reply): Likewise.
(putpkt_binary): Likewise.
(getpkt): Likewise.
(remote_add_target_side_condition): Likewise.
(remote_insert_breakpoint): Likewise.
(remote_supports_stopped_by_sw_breakpoint): Likewise.
(remote_supports_stopped_by_hw_breakpoint): Likewise.
(remote_xfer_partial): Likewise.
(remote_read_btrace): Likewise.
(remote_async_serial_handler): Likewise.
(remote_thread_events): Likewise.
(_initialize_remote): Likewise.
next reply other threads:[~2016-02-08 18:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 18:12 sergiodj+buildbot [this message]
2016-02-08 18:12 ` Failures on Debian-s390x-native-gdbserver-m64, branch master sergiodj+buildbot
2016-02-08 18:14 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-02-08 18:15 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-02-08 18:16 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2016-02-08 18:16 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2016-02-08 18:20 ` Failures on Fedora-x86_64-cxx-build-m64, " sergiodj+buildbot
2016-02-08 18:22 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-02-08 18:24 ` Failures on Debian-i686, " sergiodj+buildbot
2016-02-08 18:26 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-08 18:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-02-08 18:40 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-02-08 18:44 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-02-08 18:45 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-02-08 18:48 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-08 18:59 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-08 19:00 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-02-08 19:11 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-02-08 19:19 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-02-08 19:23 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-02-08 19:42 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
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=5488790363bf8f338e7aec4731f8bed472a2fcf9@gdb-build \
--to=sergiodj+buildbot@redhat.com \
--cc=gdb-testers@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).