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] Remove char_ptr typedef
Date: Sun, 01 Apr 2018 18:40:00 -0000 [thread overview]
Message-ID: <ec1f2d91e07522a77cbef7a438e132ff4a2a7839@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT ec1f2d91e07522a77cbef7a438e132ff4a2a7839 ***
Author: Simon Marchi <simon.marchi@polymtl.ca>
Branch: master
Commit: ec1f2d91e07522a77cbef7a438e132ff4a2a7839
Remove char_ptr typedef
Now that all instances of VEC(char_ptr) are gone, we can remove the
typedef. There is just one usage left, that is trivial to replace.
Tested by rebuilding on an enable-targets=all build.
gdb/ChangeLog:
* common/gdb_vecs.h (char_ptr): Remove.
* tracepoint.c (encode_actions_1): Remove usage of char_ptr.
next reply other threads:[~2018-04-01 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 18:40 sergiodj+buildbot [this message]
2018-04-01 18:40 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-04-01 18:41 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-04-01 18:46 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-04-01 18:48 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-04-01 18:53 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-01 19:00 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-01 19:03 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-04-01 19:20 ` Failures on Ubuntu-AArch32-native-gdbserver-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=ec1f2d91e07522a77cbef7a438e132ff4a2a7839@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).