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 for symtab_fns
Date: Wed, 11 Oct 2017 14:08:00 -0000 [thread overview]
Message-ID: <905014d7205d4f171c5cabf695fe1ec3da9b33d3@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 905014d7205d4f171c5cabf695fe1ec3da9b33d3 ***
Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 905014d7205d4f171c5cabf695fe1ec3da9b33d3
Use std::vector for symtab_fns
Simple replacement of VEC with std::vector.
gdb/ChangeLog:
* symfile.c (registered_sym_fns): Make struct, not typedef.
(DEF_VEC_O (registered_sym_fns)): Remove.
(symtab_fns): Change type to std::vector.
(add_symtab_fns): Adjust.
(find_sym_fns): Adjust.
next reply other threads:[~2017-10-11 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 14:08 sergiodj+buildbot [this message]
2017-10-11 14:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-10-11 14:37 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-10-11 14:50 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-10-11 14:58 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-11 15:01 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-11 15:11 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-10-11 15:26 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-11 15:32 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-10-11 15:47 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-29 3:39 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2017-11-29 10:05 ` Failures on Fedora-ppc64be-native-extended-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=905014d7205d4f171c5cabf695fe1ec3da9b33d3@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: link
Be 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).