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] tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p Date: Wed, 27 Dec 2017 17:51:00 -0000 [thread overview] Message-ID: <cef0f8684e818f8b6c71c44dc9cc28a6d0ac3754@gdb-build> (raw) *** TEST RESULTS FOR COMMIT cef0f8684e818f8b6c71c44dc9cc28a6d0ac3754 *** Author: Stafford Horne <shorne@gmail.com> Branch: master Commit: cef0f8684e818f8b6c71c44dc9cc28a6d0ac3754 tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p tdesc_register_in_reggroup_p in now able to handle arbitrary groups. This is useful when groups are created while the target descriptor file is received from the remote. This can be the case of a soft core target processor where registers/groups can change. gdb/ChangeLog: yyyy-mm-dd Franck Jullien <franck.jullien@gmail.com> Stafford Horne <shorne@gmail.com> * target-descriptions.c (tdesc_register_in_reggroup_p): Support arbitrary strings. (tdesc_use_registers): Add logic to register new reggroups. (tdesc_reg::group): Update comment to indicate we allow arbitrary strings. * NEWS (Changes since GDB 8.0): Announce that GDB supports arbitrary reggroups. gdb/testsuite/ChangeLog: yyyy-mm-dd Stafford Horne <shorne@gmail.com> * gdb.xml/extra-regs.xml: Add example foo reggroup. * gdb.xml/tdesc-regs.exp: Add test to check for foo reggroup. gdb/doc/ChangeLog: yyyy-mm-dd Stafford Horne <shorne@gmail.com> * gdb.texinfo (Target Description Format): Explain that arbitrary strings are now allowed for register groups.
next reply other threads:[~2017-12-27 17:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-27 17:51 sergiodj+buildbot [this message] 2017-12-27 17:51 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot 2017-12-27 17:52 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-27 17:56 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-12-27 18:06 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-12-27 18:13 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-12-27 19:03 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-12-27 19:40 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-12-27 23:07 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-12-27 23:51 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-12-28 0:29 ` 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=cef0f8684e818f8b6c71c44dc9cc28a6d0ac3754@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).