public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] remote: Make readahead_cache a C++ class
Date: Tue, 22 May 2018 22:50:00 -0000 [thread overview]
Message-ID: <dd194f6b36727987dc7f0d707512bd886982099c@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT dd194f6b36727987dc7f0d707512bd886982099c ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: dd194f6b36727987dc7f0d707512bd886982099c
remote: Make readahead_cache a C++ class
The idea here is eliminate the get_remote_state calls from within
readahead_cache_invalidate, readahead_cache_invalidate_fd,
remote_hostio_pread_from_cache by making those functions be class
methods instead. Later on we'll have one readahead_cache instance per
remote connection, and this change makes that easier.
gdb/ChangeLog:
2018-05-22 Pedro Alves <palves@redhat.com>
* remote.c (struct readahead_cache) <invalidate, invalidate_fd,
pread>: New method declarations.
(remote_target::open_1): Adjust.
(readahead_cache_invalidate): Rename to ...
(readahead_cache::invalidate): ... this, and adjust to be a class
method.
(readahead_cache_invalidate_fd): Rename to ...
(readahead_cache::invalidate_fd): ... this, and adjust to be a
class method.
(remote_hostio_pwrite): Adjust.
(remote_hostio_pread_from_cache): Rename to ...
(readahead_cache::pread): ... this, and adjust to be a class
method.
(remote_hostio_close): Adjust.
next reply other threads:[~2018-05-22 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 22:50 sergiodj+buildbot [this message]
2018-05-22 22:50 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-05-22 23:26 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2018-05-24 0:10 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-05-24 0:11 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-06-01 8:56 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-06-01 9:07 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-06-01 9:14 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2018-06-01 9:17 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-06-01 9:41 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-08-13 21:08 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-08-14 0:34 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " 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=dd194f6b36727987dc7f0d707512bd886982099c@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--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).