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] MIPS: Reorder ABI determination ahead of target description loading
Date: Mon, 26 Feb 2018 19:59:00 -0000 [thread overview]
Message-ID: <37c33887bda54afb8fbf4786d400ce549c0e3de8@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 37c33887bda54afb8fbf4786d400ce549c0e3de8 ***
Author: Maciej W. Rozycki <macro@mips.com>
Branch: master
Commit: 37c33887bda54afb8fbf4786d400ce549c0e3de8
MIPS: Reorder ABI determination ahead of target description loading
Move ABI determination code ahead of target description loading so that
architecture information can be adjusted according to the ABI selected,
and then used in OS dependent register information initialization needed
for target description processing. No functional change.
gdb/
* gdb/mips-tdep.c (mips_gdbarch_init): Reorder ABI determination
ahead of target description loading.
next reply other threads:[~2018-02-26 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 19:59 sergiodj+buildbot [this message]
2018-02-26 19:59 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-26 23:29 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-27 2:15 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-02-27 2:16 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-02-27 2:17 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-02-27 2:31 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-02-27 2:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-27 3:16 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-02-28 0:55 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-28 1:21 ` 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=37c33887bda54afb8fbf4786d400ce549c0e3de8@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).