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 free_char_ptr_vec Date: Sat, 03 Mar 2018 08:16:00 -0000 [thread overview] Message-ID: <54693cf5f11bf292ae308604caf6e866dbb03e6f@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 54693cf5f11bf292ae308604caf6e866dbb03e6f *** Author: Simon Marchi <simon.marchi@polymtl.ca> Branch: master Commit: 54693cf5f11bf292ae308604caf6e866dbb03e6f Remove free_char_ptr_vec Nothing is using it anymore. gdb/ChangeLog: * common/gdb_vecs.c (free_char_ptr_vec): Remove. * common/gdb_vecs.h (free_char_ptr_vec): Remove.
next reply other threads:[~2018-03-03 8:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-03 8:16 sergiodj+buildbot [this message] 2018-03-03 8:16 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot 2018-03-03 8:31 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-03 8:51 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-03-03 8:52 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-03-03 8:53 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-03-03 9:11 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-03-03 9:15 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-03-03 10:51 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-03 11:18 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-03-03 11:44 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2018-03-07 4:03 ` Failures on Ubuntu-AArch64-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=54693cf5f11bf292ae308604caf6e866dbb03e6f@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).