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 field lists in dwarf2read.c Date: Mon, 12 Mar 2018 03:49:00 -0000 [thread overview] Message-ID: <be2daae6b8df45f3f6de5d94a1938cef54336a72@gdb-build> (raw) *** TEST RESULTS FOR COMMIT be2daae6b8df45f3f6de5d94a1938cef54336a72 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: be2daae6b8df45f3f6de5d94a1938cef54336a72 Use std::vector for field lists in dwarf2read.c This changes dwarf2read.c to use std::vector rather than a linked list when managing the fields and base classes to be added to a type. This removes some bookkeeping types and also allows the removal of some cleanups. gdb/ChangeLog 2018-03-11 Tom Tromey <tom@tromey.com> * dwarf2read.c (struct nextfield): Add initializers. (struct nextfnfield): Remove. (struct fnfieldlist): Add initializers. Remove "length" and "head", use std::vector. (struct decl_field_list): Remove. (struct field_info): Add initializers. <fields, baseclasses>: Now std::vector. <nbaseclasses, nfnfields, typedef_field_list_count, nested_types_list_count>: Remove. (dwarf2_add_field, dwarf2_add_type_defn) (dwarf2_attach_fields_to_type, dwarf2_add_member_fn) (dwarf2_attach_fn_fields_to_type, handle_struct_member_die) (process_structure_scope): Update.
next reply other threads:[~2018-03-12 3:49 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-12 3:49 sergiodj+buildbot [this message] 2018-03-12 3:49 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2018-03-12 4:05 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-03-12 4:27 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-03-12 4:35 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-03-12 4:56 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-03-12 4:56 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-12 4:57 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-12 4:59 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-03-12 5:17 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-03-12 5:22 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-03-12 5:48 ` 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=be2daae6b8df45f3f6de5d94a1938cef54336a72@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).