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: fix Disp8 handling for scalar AVX512_4FMAPS insns
Date: Wed, 10 Jan 2018 14:58:00 -0000 [thread overview]
Message-ID: <cbda583ada32e16bf8b6c6aff730cc9eab63b364@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT cbda583ada32e16bf8b6c6aff730cc9eab63b364 ***
Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: cbda583ada32e16bf8b6c6aff730cc9eab63b364
x86: fix Disp8 handling for scalar AVX512_4FMAPS insns
Just like their packed counterparts the memory operand is always 16
bytes wide, and the Disp8 scaling is the same for all of them. (As a
side note: I'm also surprised by there being AVX512VL variants of
these as well as the AVX512_4VNNIW ones - the SDM doesn't define any
such.)
Adjust the test cases also for the packed forms to actually live up to
their promise of testing correct Disp8 encoding.
next reply other threads:[~2018-01-10 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 14:58 sergiodj+buildbot [this message]
2018-01-10 14:58 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2018-01-10 15:11 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-10 15:39 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-01-10 15:50 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-01-10 16:27 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-10 17:41 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-10 18:29 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-01-10 19:02 ` 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=cbda583ada32e16bf8b6c6aff730cc9eab63b364@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).