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 internal_complaint Date: Wed, 23 May 2018 15:59:00 -0000 [thread overview] Message-ID: <2b9496b2b4781b21bc30a70337e24205f8a923d8@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 2b9496b2b4781b21bc30a70337e24205f8a923d8 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: 2b9496b2b4781b21bc30a70337e24205f8a923d8 Remove internal_complaint I happened to notice that gdb has both complaint_internal and internal_complaint. The latter is unused, so this patch removes it. gdb/ChangeLog 2018-05-23 Tom Tromey <tom@tromey.com> * complaints.c (internal_complaint): Remove. * complaints.h (internal_complaint): Remove.
next reply other threads:[~2018-05-23 15:54 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-23 15:59 sergiodj+buildbot [this message] 2018-05-23 16:31 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-05-23 16:31 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-05-24 14:52 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-05-24 15:01 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-05-24 15:01 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-06-01 18:37 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-06-01 18:39 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-06-01 18:39 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-06-01 20:57 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2018-08-19 13:53 ` 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=2b9496b2b4781b21bc30a70337e24205f8a923d8@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).