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 on tdesc->reg_defs (gdbserver/tdesc.h)
Date: Sat, 16 Sep 2017 04:36:00 -0000 [thread overview]
Message-ID: <c4dfafabc575f4995a5aa18241adc275e63c846c@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT c4dfafabc575f4995a5aa18241adc275e63c846c ***
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: c4dfafabc575f4995a5aa18241adc275e63c846c
Use std::vector on tdesc->reg_defs (gdbserver/tdesc.h)
This is a followup patch to the build breakage fix on AArch64. While
doing the fix, I found it better to convert tdesc->reg_defs (on
gdbserver/tdesc.h) from using VEC to using std::vector. This makes
the code easier to read and maintain, and also is one more step
towards the C++fication.
Regtested on BuildBot.
2017-09-16 Sergio Durigan Junior <sergiodj@redhat.com>
* regcache.c (get_thread_regcache): Update code to use "std::vector"
instead of "VEC" for "target_desc.reg_defs".
(regcache_cpy): Likewise.
(registers_to_string): Likewise.
(registers_from_string): Likewise.
(find_regno): Likewise.
(supply_regblock): Likewise.
(regcache_raw_read_unsigned): Likewise.
* tdesc.c (init_target_desc): Likewise.
(tdesc_create_reg): Likewise.
* tdesc.h: Remove declaration of "tdesc_reg_p". Include <vector>.
(struct target_desc) <reg_defs>: Convert to "std::vector".
(target_desc): Do not initialize "reg_defs".
(~target_desc): Update code to use "std::vector" instead of "VEC"
for "target_desc.reg_defs".
(operator==): Likewise.
next reply other threads:[~2017-09-16 4:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 4:36 sergiodj+buildbot [this message]
2017-09-16 4:16 ` Failures on Fedora-x86_64-cc-with-index, branch master sergiodj+buildbot
2017-09-16 4:37 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-09-16 4:41 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-09-16 4:43 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-09-16 4:54 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-09-16 5:05 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-09-16 9:05 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-09-16 9:53 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-09-16 10:25 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-09-16 12:09 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-06 14:01 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2017-10-06 23:08 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-10-07 8:16 ` Failures on Debian-s390x-native-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=c4dfafabc575f4995a5aa18241adc275e63c846c@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).