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 and std::string instead of VEC(char_ptr) in gdbserver tdesc
Date: Sat, 31 Mar 2018 01:27:00 -0000	[thread overview]
Message-ID: <17d08cd4137063dbc43d9989b9a5cb315171174f@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 17d08cd4137063dbc43d9989b9a5cb315171174f ***

Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: 17d08cd4137063dbc43d9989b9a5cb315171174f

Use std::vector and std::string instead of VEC(char_ptr) in gdbserver tdesc

This is a straightforward replacement, no change in behavior are
intended/expected.

gdb/gdbserver/ChangeLog:

	* tdesc.h (struct target_desc) <features>: Change type to
	std::vector<std::string>.
	* tdesc.c (target_desc::~target_desc): Adjust to std::vector
	changes.
	(tdesc_get_features_xml): Likewise.
	(tdesc_create_feature): Likewise.


             reply	other threads:[~2018-03-31  1:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-31  1:27 sergiodj+buildbot [this message]
2018-03-31  1:27 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2018-03-31  1:29 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-03-31  1:36 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-03-31  1:38 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-03-31  2:00 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-03-31  2:50 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-31  3:05 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-03-31  6:18 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-31  6:44 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-03-31  7:10 ` Failures on Ubuntu-AArch32-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=17d08cd4137063dbc43d9989b9a5cb315171174f@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).