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: fold various non-memory operand AVX512VL templates
Date: Thu, 26 Apr 2018 09:03:00 -0000	[thread overview]
Message-ID: <e2195274d4a0752459ea89ffbf50b2704fb0c0b4@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT e2195274d4a0752459ea89ffbf50b2704fb0c0b4 ***

Author: Jan Beulich <jbeulich@novell.com>
Branch: master
Commit: e2195274d4a0752459ea89ffbf50b2704fb0c0b4

x86: fold various non-memory operand AVX512VL templates

There's little point carrying up to three templates per insn flavor
when the sole difference is operand size and the dependency on AVX512VL
being enabled. Instead the need for AVX512VL can be derived from an
operand allowing for ZMMword as well as one or both or XMMword and
YMMword (irrespective of whether this is a register or memory operand).
Without further abstraction to deal with the different Disp8MemShift
values between the templates, only a limited set (mostly ones only
allowing for non-memory operands) can be folded, which is being done
here.

Also drop IgnoreSize wherever possible from anything that's being
touched anyway.


             reply	other threads:[~2018-04-26  9:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26  9:03 sergiodj+buildbot [this message]
2018-04-26  9:00 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2018-04-26  9:20 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2018-04-26 13:02 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-04-26 13:18 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-04-26 13:28 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-04-26 13:28 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master sergiodj+buildbot
2018-04-26 13:36 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-04-26 13:45 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-04-26 13:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-04-26 15:37 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-04-27  7:46 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-04-27  8:24 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-04-27  9:52 ` 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=e2195274d4a0752459ea89ffbf50b2704fb0c0b4@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).