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] S390: Add guarded-storage register support to gdbserver
Date: Mon, 25 Sep 2017 17:02:00 -0000 [thread overview]
Message-ID: <ad3396348e0ebb61fdf71cff307bac08175ed366@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT ad3396348e0ebb61fdf71cff307bac08175ed366 ***
Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: ad3396348e0ebb61fdf71cff307bac08175ed366
S390: Add guarded-storage register support to gdbserver
Enable gdbserver to deal with the new guarded-storage register sets.
gdb/gdbserver/ChangeLog:
* configure.srv (s390*-*-linux*): Add s390-gs-linux64.o and
s390x-gs-linux64.o to srv_regobj. Add s390-gs-linux64.xml,
s390x-gs-linux64.xml, s390-gs.xml, and s390-gsbc.xml to
srv_xmlfiles. Add s390-gs-linux64-ipa.o and
s390x-gs-linux64-ipa.o to ipa_obj.
* linux-s390-low.c (HWCAP_S390_GS): New define.
(s390_fill_gs, s390_store_gs, s390_fill_gsbc, s390_store_gsbc):
New functions.
(s390_regsets): Add regsets for NT_S390_GS_CB and NT_S390_GS_BC.
(s390_arch_setup): Check for guarded-storage support and choose
appropriate tdesc.
(initialize_low_arch): Invoke init_registers_s390_gs_linux64 and
init_registers_s390x_gs_linux64.
* linux-s390-tdesc.h (enum s390_linux_tdesc) <S390_TDESC_GS>: New
enum value.
(init_registers_s390x_gs_linux64, tdesc_s390x_gs_linux64)
(init_registers_s390_gs_linux64, tdesc_s390_gs_linux64): Declare.
next reply other threads:[~2017-09-25 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 17:02 sergiodj+buildbot [this message]
2017-09-25 17:06 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot
2017-09-25 17:12 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-09-25 17:14 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-09-25 17:21 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-09-25 17:26 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-09-25 17:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-09-25 17:50 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-09-25 18:06 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-09-25 20:23 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-09-25 20:47 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-09-25 22:48 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-09-26 0:35 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-09-26 0:35 ` Failures on Ubuntu-AArch32-native-extended-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=ad3396348e0ebb61fdf71cff307bac08175ed366@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).