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] Use std::vector in end_symtab_get_static_block Date: Mon, 16 Oct 2017 22:35:00 -0000 [thread overview] Message-ID: <b05628f0a878cdd64492bbc49d60003d699763ad@gdb-build> (raw) *** TEST RESULTS FOR COMMIT b05628f0a878cdd64492bbc49d60003d699763ad *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: b05628f0a878cdd64492bbc49d60003d699763ad Use std::vector in end_symtab_get_static_block Change end_symtab_get_static_block to use std::vector. This removes a cleanup. ChangeLog 2017-10-16 Tom Tromey <tom@tromey.com> * buildsym.c (block_compar): Remove. (end_symtab_get_static_block): Use std::vector.
next reply other threads:[~2017-10-16 22:35 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-16 22:35 sergiodj+buildbot [this message] 2017-10-16 22:35 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-10-16 22:36 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-10-16 22:44 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-16 23:00 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-16 23:12 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-10-16 23:24 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-10-18 20:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-10-18 21:01 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-10-18 21:03 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-10-18 21:17 ` Failures on Fedora-x86_64-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=b05628f0a878cdd64492bbc49d60003d699763ad@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).