public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Add support for extensions in the .machine pseudoop on S/390, e.g. ".machine zEC12+nohtm+vx"
Date: Tue, 29 Sep 2015 13:41:00 -0000 [thread overview]
Message-ID: <7ecc513a44095d614f10e89c67d9be5826abacf9@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 7ecc513a44095d614f10e89c67d9be5826abacf9 ***
Author: Dominik Vogt <vogt@linux.vnet.ibm.com>
Branch: master
Commit: 7ecc513a44095d614f10e89c67d9be5826abacf9
Add support for extensions in the .machine pseudoop on S/390, e.g. ".machine zEC12+nohtm+vx"
gas * doc/c-s390.texi: Add documentation.
Add missing code markup.
* config/tc-s390.c (current_flags): New static variable.
(s390_parse_cpu): Parse cpu flags a la "+nohtm" etc.
(s390_setup_opcodes): Use cpu flags to determine the set of opcodes.
Fix indentation.
(md_parse_option): Call s390_parse_cpu with the new signature.
(s390_machine): Likewise.
Keep track of current_flags.
Simplify code a bit.
undefine MAX_HISTORY at end of function.
(s390_machinemode): undefine MAX_HISTORY at end of function.
Update an error message.
tests * gas/s390/s390.exp: Add new tests.
* gas/s390/machine-parsing-1.s: New test file.
* gas/s390/machine-parsing-1.l: Likewise.
* gas/s390/machine-parsing-2.s: Likewise.
* gas/s390/machine-parsing-2.l: Likewise.
* gas/s390/machine-parsing-3.s: Likewise.
* gas/s390/machine-parsing-3.l: Likewise.
* gas/s390/machine-parsing-4.s: Likewise.
* gas/s390/machine-parsing-4.l: Likewise.
* gas/s390/machine-parsing-5.s: Likewise.
* gas/s390/machine-parsing-5.l: Likewise.
* gas/s390/machine-parsing-6.s: Likewise.
* gas/s390/machine-parsing-6.l: Likewise.
opcode * s390.h (S390_INSTR_FLAG_HTM): New flag.
(S390_INSTR_FLAG_VX): New flag.
(S390_INSTR_FLAG_FACILITY_MASK): New flag mask.
opcodes * s390-mkopc.c (main): Parse htm and vx flag.
* s390-opc.txt: Mark instructions from the hardware transactional
memory and vector facilities with the "htm"/"vx" flag.
next reply other threads:[~2015-09-29 12:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 13:41 sergiodj+buildbot [this message]
2015-09-29 16:15 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2015-09-29 16:17 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:18 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-09-29 16:18 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2015-09-29 16:22 ` Failures on Debian-i686, " sergiodj+buildbot
2015-09-29 16:26 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-09-29 16:33 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:34 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:42 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:42 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2015-09-29 16:42 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2015-09-29 16:45 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2015-09-29 16:47 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:51 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:51 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-09-29 16:52 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:54 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-09-29 16:57 ` Failures on Debian-x86_64-native-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=7ecc513a44095d614f10e89c67d9be5826abacf9@gdb-build \
--to=sergiodj+buildbot@redhat.com \
--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).