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] Change `file_symtabs' to std::vector
Date: Thu, 30 Aug 2018 00:06:00 -0000	[thread overview]
Message-ID: <2a90824133f9d46970c9c52b68ef2ccbeb6389ac@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 2a90824133f9d46970c9c52b68ef2ccbeb6389ac ***

Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 2a90824133f9d46970c9c52b68ef2ccbeb6389ac

Change `file_symtabs' to std::vector

This patch changes the `file_symtabs' members in linespec.c structures
from a VEC to a std::vector (or unique_ptr thereof), eliminating a cleanup
in the process.

gdb/ChangeLog:

	* linespec.c (symtab_vector_up): Define.
	(struct linespec) <file_symtabs>: Change type to std::vector *.
	Update all uses.
	(struct collect_info) <file_symtabs>: Likewise.
	(collect_symtabs_from_filename): Return symtab_vector_up.
	Update all callers.
	(decode_objc): Remove cleanup.
	(symtab_collector::symtab_collector): Initialize `m_symtabs'.
	(symtab_collector::release_symtabs): Return symtab_vector_up.
	Update all callers.
	(class symtab_collector) <m_symtabs>: Change type to symtab_vector_up.
	Update all users.
	(collect_symtabs_from_filename, symtabs_from_filename): Return
	symtab_vector_up.  Update all callers.


             reply	other threads:[~2018-08-29 22:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30  0:06 sergiodj+buildbot [this message]
2018-08-30  0:07 ` *** COMPILATION FAILED *** Failures on RHEL-s390x-m64, branch master *** BREAKAGE *** sergiodj+buildbot
2018-08-30  3:31 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-08-30  3:39 ` *** COMPILATION FAILED *** Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-08-30  3:42 ` *** COMPILATION FAILED *** Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-08-30  9:56 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2018-08-30 10:21 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-08-30 10:23 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-08-30 10:31 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-08-30 10:41 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-08-30 10:44 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-08-30 11:14 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-08-30 11:25 ` 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=2a90824133f9d46970c9c52b68ef2ccbeb6389ac@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).