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] x86/Intel: fix operand checking for MOVSD
Date: Fri, 01 Jul 2016 07:09:00 -0000 [thread overview]
Message-ID: <8325cc6398187c12e0fe04a68a21e4eb5f44fa20@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 8325cc6398187c12e0fe04a68a21e4eb5f44fa20 ***
Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: 8325cc6398187c12e0fe04a68a21e4eb5f44fa20
x86/Intel: fix operand checking for MOVSD
The dual purpose mnemonic (string move vs scalar double move) breaks
the assumption that the isstring flag would be set on both the first
and last entry in the current set of templates, which results in bogus
or missing diagnostics for the string move variant of the mnemonic.
Short of mostly rewriting i386_index_check() and its interaction with
the rest of the code, simply shrink the template set to just string
instructions when encountering the second memory operand, and run
i386_index_check() a second time for the first memory operand after
that reduction.
next reply other threads:[~2016-07-01 7:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 7:09 sergiodj+buildbot [this message]
2016-07-01 7:09 ` Failures on Fedora-ppc64be-cc-with-index, branch master sergiodj+buildbot
2016-07-01 7:10 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-07-01 7:15 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-07-01 7:19 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-07-01 7:24 ` Failures on Debian-i686, " sergiodj+buildbot
2016-07-01 7:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-07-01 7:28 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-07-01 7:31 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-07-01 7:39 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-07-01 7:44 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-07-01 7:52 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-07-01 7:54 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-07-01 7:55 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-07-01 8:04 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-07-01 8:17 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-07-01 9:12 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-07-17 18:35 ` Failures on Ubuntu-AArch64-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=8325cc6398187c12e0fe04a68a21e4eb5f44fa20@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).