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 make_cleanup_regcache_invalidate Date: Tue, 26 Sep 2017 03:25:00 -0000 [thread overview] Message-ID: <b292235f666ff2123e26794db73d5a27a685e7be@gdb-build> (raw) *** TEST RESULTS FOR COMMIT b292235f666ff2123e26794db73d5a27a685e7be *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: b292235f666ff2123e26794db73d5a27a685e7be Remove make_cleanup_regcache_invalidate This removes make_cleanup_regcache_invalidate in favor of a simple RAII class that handles register invalidation. gdb/ChangeLog 2017-09-25 Tom Tromey <tom@tromey.com> * regcache.c (class regcache_invalidator): New. (struct register_to_invalidate): Remove. (make_cleanup_regcache_invalidate): Remove. (regcache::raw_write): Use regcache_invalidator.
next reply other threads:[~2017-09-26 3:15 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-26 3:25 sergiodj+buildbot [this message] 2017-09-26 3:27 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2017-09-26 3:36 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-09-26 3:41 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-09-26 3:45 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-09-26 4:25 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-26 4:46 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-26 9:17 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-09-26 9:17 ` Failures on Ubuntu-AArch32-native-extended-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=b292235f666ff2123e26794db73d5a27a685e7be@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).