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] amd64: remove additional comparison for validity of a register number.
Date: Fri, 27 Jan 2017 15:16:00 -0000 [thread overview]
Message-ID: <7005d26ac72abbf12e02947ab87dbb3804f326a8@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 7005d26ac72abbf12e02947ab87dbb3804f326a8 ***
Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
Branch: master
Commit: 7005d26ac72abbf12e02947ab87dbb3804f326a8
amd64: remove additional comparison for validity of a register number.
Second part of the && is already guaranteed in the "regnum < num_regs"
due to comparison above.
2017-01-27 Walfred Tedeschi <walfred.tedeschi@intel.com>
* amd64-nat.c (amd64_native_gregset_reg_offset): Simplify logic
that checks validity of a register number.
next reply other threads:[~2017-01-27 15:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 15:16 sergiodj+buildbot [this message]
2017-01-27 15:16 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2017-01-27 15:25 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-01-27 15:26 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-01-27 15:42 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-01-27 15:42 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-01-27 15:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-01-27 15:58 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-01-27 15:58 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-01-27 16:03 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-01-27 16:10 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-01-27 16:12 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2017-01-27 16:30 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-01-27 16:49 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2017-01-27 20:40 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2017-01-27 22:28 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-01-28 7:08 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2017-01-28 8:07 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2017-01-28 10:37 ` Failures on Fedora-ppc64le-cc-with-index, " 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=7005d26ac72abbf12e02947ab87dbb3804f326a8@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).