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] Eliminate target_has_exited Date: Thu, 12 Apr 2018 16:59:00 -0000 [thread overview] Message-ID: <436411b1c6cb93541fd502321cf5470fe0392b91@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 436411b1c6cb93541fd502321cf5470fe0392b91 *** Author: Pedro Alves <palves@redhat.com> Branch: master Commit: 436411b1c6cb93541fd502321cf5470fe0392b91 Eliminate target_has_exited Nothing uses this. gdb/ChangeLog: 2018-04-12 Pedro Alves <palves@redhat.com> * target.h (target_ops::to_has_exited): Delete. (target_has_exited): Delete. * target-delegates.c: Regenerate.
next reply other threads:[~2018-04-12 16:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-12 16:59 sergiodj+buildbot [this message] 2018-04-12 16:59 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2018-04-12 17:04 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-04-12 17:15 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-04-12 17:16 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-04-12 17:20 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-12 17:21 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-04-12 17:26 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-12 17:28 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master sergiodj+buildbot 2018-04-12 18:14 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-04-12 18:30 ` Failures on Debian-s390x-native-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=436411b1c6cb93541fd502321cf5470fe0392b91@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).