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: Allocate gdbarch & tdep at start of gdbarch_init
Date: Tue, 23 Jan 2018 13:15:00 -0000 [thread overview]
Message-ID: <21f6f5ffc652e116e518fee29ebdc8fbfeeaa734@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 21f6f5ffc652e116e518fee29ebdc8fbfeeaa734 ***
Author: Philipp Rudo <prudo@linux.vnet.ibm.com>
Branch: master
Commit: 21f6f5ffc652e116e518fee29ebdc8fbfeeaa734
s390: Allocate gdbarch & tdep at start of gdbarch_init
Moving the allocation of gdbarch_tdep to the start of s390_gdbarch_init
allows us to use its fields for tracking the different features instead of
using separate variables. To make the code a little nicer move the actual
allocation and initialization to a separate function. Also move the
allocation of gdbarch to keep the two together.
gdb/ChangeLog:
* s390-linux-tdep (s390_abi_kind) <ABI_NONE>: New default field.
(gdbarch_tdep) <have_upper, have_vx>: New fields.
(s390_gdbarch_tdep_alloc): New function.
(s390_gdbarch_init): Allocate tdep at start and use its fields
instead of separate variables.
next reply other threads:[~2018-01-23 13:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 13:15 sergiodj+buildbot [this message]
2018-01-23 13:16 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-01-23 13:51 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-23 13:54 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-01-23 13:56 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-01-23 14:03 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-01-23 14:18 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-23 14:31 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-01-23 14:39 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-01-23 14:43 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-01-23 14:51 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-01-23 15:05 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-01-23 15:17 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-23 15:47 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-23 15:49 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-01-23 16:22 ` 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=21f6f5ffc652e116e518fee29ebdc8fbfeeaa734@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).