public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] x86: drop stale Vec_Imm4 related comment Date: Thu, 16 Jan 2020 11:54:00 -0000 [thread overview] Message-ID: <d0849eed78268cee12d4540c67a2d9813d44f61c@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d0849eed78268cee12d4540c67a2d9813d44f61c *** commit d0849eed78268cee12d4540c67a2d9813d44f61c Author: Jan Beulich <jbeulich@suse.com> AuthorDate: Thu Jan 16 10:07:05 2020 +0100 Commit: Jan Beulich <jbeulich@suse.com> CommitDate: Thu Jan 16 10:07:05 2020 +0100 x86: drop stale Vec_Imm4 related comment I overlooked this in commit 9d3bf266fd ("x86: drop Vec_Imm4"), presumably because of the mis-spelling. diff --git a/opcodes/ChangeLog b/opcodes/ChangeLog index b3b51c8a56..eda7fa74fb 100644 --- a/opcodes/ChangeLog +++ b/opcodes/ChangeLog @@ -1,3 +1,7 @@ +2020-01-16 Jan Beulich <jbeulich@suse.com> + + * i386-opc.tbl: Drop stale comment from XOP section. + 2020-01-16 Jan Beulich <jbeulich@suse.com> * i386-opc.tbl (movq): Add VexWIG to SSE2AVX XMM->XMM forms. diff --git a/opcodes/i386-opc.tbl b/opcodes/i386-opc.tbl index d4226fc260..73cd6c6a11 100644 --- a/opcodes/i386-opc.tbl +++ b/opcodes/i386-opc.tbl @@ -2607,8 +2607,6 @@ vfnmsubss, 4, 0x667e, None, 1, CpuFMA4, Modrm|Vex|VexOpcode=2|VexVVVV=1|VexW=2|V vfnmsubss, 4, 0x667e, None, 1, CpuFMA4, Modrm|Vex|VexOpcode=2|VexVVVV=1|VexW=1|VexSources=2|IgnoreSize|No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf, {RegXMM, Dword|Unspecified|BaseIndex|RegXMM, RegXMM, RegXMM } // XOP instructions -// We add Imm8 to Vex_Imm4. We use Imm8 to indicate that the operand -// is an immediate. We will check if its value will fit 4 bits. vfrczpd, 2, 0x81, None, 1, CpuXOP, Modrm|VexOpcode=4|VexW=1|CheckRegSize|No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|Vex, { Unspecified|BaseIndex|RegXMM|RegYMM, RegXMM|RegYMM } vfrczps, 2, 0x80, None, 1, CpuXOP, Modrm|VexOpcode=4|VexW=1|CheckRegSize|No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf|Vex, { Unspecified|BaseIndex|RegXMM|RegYMM, RegXMM|RegYMM }
next reply other threads:[~2020-01-16 11:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-16 11:54 gdb-buildbot [this message] 2020-01-16 11:51 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, branch master gdb-buildbot 2020-01-17 12:29 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-cc-with-index, branch master *** BREAKAGE *** gdb-buildbot 2020-01-17 12:31 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-m32, " gdb-buildbot 2020-01-17 12:41 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2020-01-17 12:45 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-m64, " gdb-buildbot 2020-01-17 12:48 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2020-01-17 13:18 ` Failures on Fedora-i686, branch master gdb-buildbot 2020-01-17 13:20 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** gdb-buildbot 2020-01-17 13:27 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master gdb-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=d0849eed78268cee12d4540c67a2d9813d44f61c@gdb-build \ --to=gdb-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: linkBe 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).