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] Remove regcache::m_readonly_p Date: Wed, 21 Feb 2018 13:02:00 -0000 [thread overview] Message-ID: <796bb0264184e8d9343f041c2f11cb898c0d18ac@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 796bb0264184e8d9343f041c2f11cb898c0d18ac *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: 796bb0264184e8d9343f041c2f11cb898c0d18ac Remove regcache::m_readonly_p Now, m_readonly_p is always false, so we can remove it, and regcache no longer includes pseudo registers. Some regcache methods are lift up to its parent class, like reg_buffer or detached_regcache. gdb: 2018-02-21 Yao Qi <yao.qi@linaro.org> * regcache.c (regcache::regcache): Update. (regcache::invalidate): Move it to detached_regcache::invalidate. (get_thread_arch_aspace_regcache): Update. (regcache::raw_update): Update. (regcache::cooked_read): Remove some code. (regcache::cooked_read_value): Likewise. (regcache::raw_write): Remove assert on m_readonly_p. (regcache::raw_supply_integer): Move it to detached_regcache::raw_supply_integer. (regcache::raw_supply_zeroed): Likewise. * regcache.h (detached_regcache) <raw_supply_integer>: New declaration. <raw_supply_zeroed, invalidate>: Likewise. (regcache) <raw_supply_integer, raw_supply_zeroed>: Removed. <invalidate>: Likewise. <m_readonly_p>: Removed.
next reply other threads:[~2018-02-21 13:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-21 13:02 sergiodj+buildbot [this message] 2018-02-21 13:02 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-02-21 18:34 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-02-21 19:20 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-02-21 19:33 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-21 20:14 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-02-21 20:36 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-02-22 5:31 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-22 6:04 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-02-24 0:29 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-02-24 0:59 ` Failures on Debian-s390x-native-extended-gdbserver-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=796bb0264184e8d9343f041c2f11cb898c0d18ac@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: linkBe 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).