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 I386_MAX_REGISTER_SIZE and M68K_MAX_REGISTER_SIZE
Date: Fri, 24 Feb 2017 16:32:00 -0000 [thread overview]
Message-ID: <975c21ab6d2f6e94fcd4723bcaada4015ce7b0cf@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 975c21ab6d2f6e94fcd4723bcaada4015ce7b0cf ***
Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 975c21ab6d2f6e94fcd4723bcaada4015ce7b0cf
Use I386_MAX_REGISTER_SIZE and M68K_MAX_REGISTER_SIZE
gdb/
* i386-tdep.c (i386_pseudo_register_read_into_value): Use
I386_MAX_REGISTER_SIZE.
(i386_pseudo_register_write): Likewise.
(i386_process_record): Likewise.
* i387-tdep.c (i387_supply_xsave): Likewise.
* m68k-linux-nat.c (fetch_register): Use M68K_MAX_REGISTER_SIZE.
(store_register): Likewise.
next reply other threads:[~2017-02-24 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 16:32 sergiodj+buildbot [this message]
2017-02-24 16:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2017-02-24 16:37 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-02-24 16:45 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-02-24 17:01 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-02-24 17:12 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-02-24 17:24 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-02-25 20:59 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-02-26 3:26 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2017-02-26 5:20 ` Failures on Fedora-ppc64le-native-extended-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=975c21ab6d2f6e94fcd4723bcaada4015ce7b0cf@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).