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_save and regcache_cpy Date: Wed, 21 Feb 2018 12:00:00 -0000 [thread overview] Message-ID: <fc5b87361580d915e28ae5f3cc4794b75b671b5a@gdb-build> (raw) *** TEST RESULTS FOR COMMIT fc5b87361580d915e28ae5f3cc4794b75b671b5a *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: fc5b87361580d915e28ae5f3cc4794b75b671b5a Remove regcache_save and regcache_cpy ... instead we start to use regcache methods save and restore. It is quite straightforward to replace regcache_save with regcache->save. regcache_cpy has some asserts, some of them not necessary, like gdb_assert (src != dst); because we already assert !m_readonly_p and src->m_readonly_p, so src isn't dst. Some of the asserts are moved to ::restore. gdb: 2018-02-21 Yao Qi <yao.qi@linaro.org> * frame.c (frame_save_as_regcache): Use regcache method save. (frame_pop): Use regcache method restore. * infrun.c (restore_infcall_suspend_state): Likewise. * linux-fork.c (fork_load_infrun_state): Likewise. * ppc-linux-tdep.c (ppu2spu_sniffer): User regcache method save. * regcache.c (regcache_save): Remove. (regcache::restore): More asserts. (regcache_cpy): Remove. * regcache.h (regcache_save): Remove the declaration. (regcache::restore): Move from private to public. Remove the friend declaration of regcache_cpy. (regcache_cpy): Remove declaration.
next reply other threads:[~2018-02-21 12:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-21 12:00 sergiodj+buildbot [this message] 2018-02-21 12:00 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-02-21 12:46 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-02-21 13:21 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-02-21 13:23 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-02-21 13:25 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-02-21 13:43 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-02-21 13:49 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-02-21 17:26 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-21 18:22 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-02-21 19:19 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2018-02-22 23:37 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-02-23 0:22 ` 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=fc5b87361580d915e28ae5f3cc4794b75b671b5a@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).