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] Replace CET bit with IBT and SHSTK bits.
Date: Wed, 17 Jan 2018 17:04:00 -0000 [thread overview]
Message-ID: <d777820bf5abea433c36e956b53b299502e0f708@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT d777820bf5abea433c36e956b53b299502e0f708 ***
Author: Igor Tsimbalist <igor.v.tsimbalist@intel.com>
Branch: master
Commit: d777820bf5abea433c36e956b53b299502e0f708
Replace CET bit with IBT and SHSTK bits.
The latest specification for Intel CET technology defined two
new bits instead of previously used CET bit. These are IBT and
SHSTK bits. The patch replaces CET bit with IBT and SHSTK bits.
gas/
* config/tc-i386.c (cpu_arch): Delete .cet. Add .ibt, .shstk.
(cpu_noarch): Add noibt, noshstk.
(parse_insn): Change cpucet to cpuibt.
* doc/c-i386.texi: Delete .cet. Add .ibt, .shstk.
* testsuite/gas/i386/cet-ibt-inval.l: New test.
* testsuite/gas/i386/cet-ibt-inval.s: Likewise.
* testsuite/gas/i386/cet-shstk-inval.l: Likewise.
* testsuite/gas/i386/cet-shstk-inval.s: Likewise.
* testsuite/gas/i386/x86-64-cet-ibt-inval.l: Likewise.
* testsuite/gas/i386/x86-64-cet-ibt-inval.s: Likewise.
* testsuite/gas/i386/x86-64-cet-shstk-inval.l: Likewise.
* testsuite/gas/i386/x86-64-cet-shstk-inval.s: Likewise.
opcodes/
* i386-gen.c (cpu_flag_init): Delete CPU_CET_FLAGS,
CpuCET. Add CPU_IBT_FLAGS, CPU_SHSTK_FLAGS, CPY_ANY_IBT_FLAGS,
CPU_ANY_SHSTK_FLAGS, CpuIBT, CpuSHSTK.
(cpu_flags): Add CpuIBT, CpuSHSTK.
* i386-opc.h (enum): Add CpuIBT, CpuSHSTK.
(i386_cpu_flags): Add cpuibt, cpushstk.
* i386-opc.tbl: Change CpuCET to CpuSHSTK and CpuIBT.
* i386-init.h: Regenerate.
* i386-tbl.h: Likewise.
next reply other threads:[~2018-01-17 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:04 sergiodj+buildbot [this message]
2018-01-17 17:04 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-01-17 17:24 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-17 17:24 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-01-17 17:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-01-17 17:38 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-01-17 17:39 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-01-17 17:53 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-01-17 18:08 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-17 18:22 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-01-17 18:27 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-01-17 22:13 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-18 4:15 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-18 4:52 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-01-18 5:20 ` 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=d777820bf5abea433c36e956b53b299502e0f708@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).